-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[Flutter GPU] Fix Android/GLES crashers. #172588
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
base: master
Are you sure you want to change the base?
Conversation
@@ -88,12 +88,12 @@ struct TexImage2DData { | |||
type = GL_UNSIGNED_BYTE; | |||
break; | |||
case PixelFormat::kR32G32B32A32Float: | |||
internal_format = GL_RGBA; | |||
internal_format = GL_RGBA32F; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does some form of capability checking already exist for these?
Fixing the enum values here sgtm though.
@@ -75,7 +75,9 @@ class TextureGLES final : public Texture, | |||
std::shared_ptr<ReactorGLES> reactor, | |||
TextureDescriptor desc); | |||
|
|||
TextureGLES(std::shared_ptr<ReactorGLES> reactor, TextureDescriptor desc); | |||
TextureGLES(std::shared_ptr<ReactorGLES> reactor, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's document the argument. Something like, "Whether the calling thread has a reactor worker.". Or something that ties the usage to the way the reactor works.
Thinking about this some more, can't this value be implicitly determined using ReactorGLES::CanReactOnCurrentThread
?
Continuation of #165630.
Resolves #164278.
Resolves bdero/flutter_scene#35.
Partly fixes: #160948.