Skip to content

embedder_surface_gl Error #172

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
alexelisenko opened this issue Jun 28, 2019 · 3 comments
Closed

embedder_surface_gl Error #172

alexelisenko opened this issue Jun 28, 2019 · 3 comments

Comments

@alexelisenko
Copy link

I am getting the following error:

[ERROR:flutter/shell/platform/embedder/embedder_surface_gl.cc(89)] Could not create a resource context for async texture uploads. Expect degraded performance. Set a valid make_resource_current callback on FlutterOpenGLRendererConfig.
Flutter 1.7.10-pre.19 • channel master • https://github.com/flutter/flutter.git
Framework • revision 305a99501e (3 days ago) • 2019-06-25 18:20:39 -0400
Engine • revision 107fe82343
Tools • Dart 2.4.0

I see that this might have been resolved in: #68 , but not sure on how to debug this. Any help would be appreciated.

@pchampio
Copy link
Member

This error isn't critical, it doesn't have any effect on go-flutter-desktop.

Closing since it's a duplicate of #82

@alexelisenko
Copy link
Author

@Drakirus I probably should have added more details. I dont know if that error is related to my issue, but, on Mac OS 10.14.5, when I build with flutter, the UI is very responsive and I never have any missed mouse clicks, but when I use go-flutter, the UI misses mouse clicks almost 20-30% of the time.

Since that error mentioned performance, I thought it may be related, if it not, then are there any build differences between flutter and go-flutter that would cause this?

@GeertJohan
Copy link
Member

I don't think it's related, but this is indeed an issue I have been noticing recently. Likely a regression we recently made. I'll be opening a new issue for this problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants