Crash on enter VR with compositor context error |
|||||||||||||
Issue descriptionChrome Version: 61.0.3142.0 (dev build from sha 56ab4c1ae8f3) OS: Android O 8.0.0 What steps will reproduce the problem? (1) Start Chrome (2) Insert device into Daydream headset What is the expected result? Enters VR normally What happens instead? Crash [FATAL:compositor_impl_android.cc(760)] Too many context creation failures. Giving up... See attached stack trace for more. This is currently repro'ing 100% for me, but when I first started with this build it didn't happen (might have something to do with playing multiple videos from m.youtube and switching between fullscreen a lot).
,
Jun 26 2017
,
Jun 28 2017
,
Jun 28 2017
need the gpu process crash log, but might be crbug.com/722962
,
Jun 28 2017
Not crbug.com/722962 06-28 10:12:04.484 4956 4977 E libEGL : eglCreateWindowSurface: native_window_api_connect (win=0xde2f5808) failed (0xffffffed) (already connected to another API?) 06-28 10:12:04.484 4956 4977 E libEGL : eglCreateWindowSurface:491 error 3003 (EGL_BAD_ALLOC) 06-28 10:12:04.484 4956 4977 E chromium: [ERROR:gl_surface_egl.cc(827)] eglCreateWindowSurface failed with error EGL_BAD_ALLOC 06-28 10:12:04.485 4956 4977 E chromium: [ERROR:gpu_command_buffer_stub.cc(686)] Failed to create surface. Sounds like it's trying to create a second egl surface out of the same window handle, something like that? That's probably wrong
,
Jun 28 2017
,
Jun 28 2017
I'm seeing this too, but my vrcore is 1.6.160172134.
,
Jun 28 2017
Attempting a bisect.
,
Jun 29 2017
Builds that used to work are failing now, so I'm having trouble bisecting. I had an O update when this started failing. However, canary is still working for me, so it appears to be dev-build only. changing gn args didn't help. building monochrome_apk or chrome_apk works fine, but chrome_public_apk doesn't, so the issue is around src-internal (perhaps a bad file that is sticking around?).
,
Jun 29 2017
I synced to ToT again (7bda9a5b4c91) and am no longer able to repro this on my device.
,
Jun 29 2017
I take back that I couldn't repro with chrome_apk. It still repros, just not 100% of the time. Trying to sync later per Adam's suggestion.
,
Jul 7 2017
After not being able to repro last week I started seeing this again with a build from yesterday.
,
Jul 7 2017
,
Jul 7 2017
,
Jul 7 2017
I was able to go back to 7bda9a5b4c91 and see it working correctly again, so I may be able to bisect this.
,
Jul 7 2017
And now I can no longer repro (after bisecting and getting back to a point past where I saw it fail in comment #13). Not sure what to do with this now. In the meantime I think we can drop the priority until it repros more often or more reliably.
,
Jul 10 2017
,
Jul 11 2017
,
Jul 11 2017
,
Jul 12 2017
Can't reproduce. Please re-open if you start seeing this again.
,
Jul 4
|
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by amp@chromium.org
, Jun 26 2017