Open tetious opened 3 months ago
Have you filed an issue for Chromium? It would make sense to make Chromium devs aware of the bug.
Have you filed an issue for Chromium? It would make sense to make Chromium devs aware of the bug.
Unfortunately I don't think I have enough context as to what is happening within Godot when this failure occurs to create a useful bug report for the Chromium folks.
Maybe someone with more low-level engine experience can report it? (or summarize the problem in a way that would be useful for the Chromium devs?)
You worry too much. You have an MRP for Chromium folks to (try to) reproduce the issue They are professionals, surely they have the tools and technical know-how to figure out what is happening. Please just file the issue with what you have. If they do want more information, they will ask.
@tetious Can you report this on chromium.org? Thanks in advance :slightly_smiling_face:
Chromium issue: https://issues.chromium.org/issues/359912067
This is fixed for me in Chrome 128. Is this still a problem for you, @Dev0mi ?
Tested versions
System information
MacOs 14.5, Chrome 127.0.6533.89
Issue description
When a
SubViewport
under aSubViewportContainer
is visible in a scene, on a Mac that is using the "new" Metal ANGLE backend by default, Chrome's GL context immediately crashes and logs a bunch of errors: https://gist.github.com/tetious/48c29263af9202fac48049c04f1b160cThis only occurs when the ANGLE graphics backend is set to Metal or left to the default (at least for my two test Macs) in chrome://flags. If the backend is set to OpenGL, it works normally.
Steps to reproduce
Run the attached MRP on a Mac with Chrome by using the "Remote Debug" -> Run in browser feature. It should fail immediately.
SubViewportContainer
invisible -> does not fail (but viewport doesn't show)Minimal reproduction project (MRP)
subviewtest.zip Repro URL: https://orcling.com/subview-godot/