Issue metadata
Sign in to add a comment
|
Hitting xr_frame_provider DCHECK on Oreo |
||||||||||||||||||||||||||
Issue descriptionOreo Phone Tester has been hitting this DCHECK pretty regularly in some WebXR tests https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/xr/xr_frame_provider.cc?q=xr_frame_provider.cc&sq=package:chromium&dr&l=388. This is reproducible locally be running VrBrowserTransitionTest#testExitPresentationWebXrToVrShell repeatedly on a Pixel 2 with Oreo. This appears to be happening when trying to exit a WebXR immersive session. Running the stack trace through the stack tool isn't providing any information (not even a garbage symbolized stack), but I'll keep trying to get a stack.
,
Jul 27
Still can't get a useful stack. It's in a weird format that's different from other native stacks I've seen. 07-27 13:47:50.305 23987 24006 E FrameEvents: updateAcquireFence: Did not find frame. 07-27 13:47:50.314 23926 23926 E chromium: [ERROR:display_scheduler.cc(305)] Not implemented reached in virtual void viz::DisplayScheduler::OnBeginFrameSourcePausedChanged(bool) 07-27 13:47:50.365 23958 23972 F chromium: [FATAL:xr_frame_provider.cc(389)] Check failed: !frame_transport_->DrawingIntoSharedBuffer() || buffer_mailbox_holder_. 07-27 13:47:50.365 23958 23972 F chromium: #00 0x00000073aed6bc57 /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x00000000056c9c57 07-27 13:47:50.365 23958 23972 F chromium: #01 0x00000073b1c3fcdf /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x000000000859dcdf 07-27 13:47:50.365 23958 23972 F chromium: #02 0x00000073b1c4111f /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x000000000859f11f 07-27 13:47:50.365 23958 23972 F chromium: #03 0x00000073acba116b /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x00000000034ff16b 07-27 13:47:50.365 23958 23972 F chromium: #04 0x00000073ae8d0b5b /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x000000000522eb5b 07-27 13:47:50.365 23958 23972 F chromium: #05 0x00000073acba116b /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x00000000034ff16b 07-27 13:47:50.365 23958 23972 F chromium: #06 0x00000073aed5b59b /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x00000000056b959b 07-27 13:47:50.365 23958 23972 F chromium: #07 0x00000073aedb3f43 /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x0000000005711f43 07-27 13:47:50.365 23958 23972 F chromium: #08 0x00000073acba116b /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x00000000034ff16b 07-27 13:47:50.365 23958 23972 F chromium: #09 0x00000073aed5b59b /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x00000000056b959b 07-27 13:47:50.365 23958 23972 F chromium: #10 0x00000073aed74f17 /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x00000000056d2f17 07-27 13:47:50.365 23958 23972 F chromium: #11 0x00000073aed75213 /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x00000000056d3213 07-27 13:47:50.365 23958 23972 F chromium: #12 0x00000073aed75367 /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x00000000056d3367 07-27 13:47:50.365 23958 23972 F chromium: #13 0x00000073aed7777b /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x00000000056d577b 07-27 13:47:50.365 23958 23972 F chromium: #14 0x00000073aed74b43 /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x00000000056d2b43 07-27 13:47:50.365 23958 23972 F chromium: #15 0x00000073aed92df7 /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x00000000056f0df7 07-27 13:47:50.365 23958 23972 F chromium: #16 0x00000073b1de3d2b /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x0000000008741d2b 07-27 13:47:50.365 23958 23972 F chromium: #17 0x00000073aea617f7 /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x00000000053bf7f7 07-27 13:47:50.365 23958 23972 F chromium: #18 0x00000073afe535b7 /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x00000000067b15b7 07-27 13:47:50.365 23958 23972 F chromium: #19 0x00000073aea60a27 /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/base.apk+0x00000000053bea27 07-27 13:47:50.365 23958 23972 F chromium: #20 0x00000073b2b9547b /data/app/org.chromium.chrome-6FAxmTGLfzB2jKHSx6R0Yg==/oat/arm64/base.odex+0x000000000005447b
,
Jul 27
,
Jul 27
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b1471eca807da2c487f3fd775dd0232e0d9006c0 commit b1471eca807da2c487f3fd775dd0232e0d9006c0 Author: Klaus Weidner <klausw@chromium.org> Date: Fri Jul 27 23:20:24 2018 Avoid DCHECK failure on WebXR immersive session transition The first frame of an immersive session may not yet have frame data including the expected frame_id and output buffer mailbox holder, don't treat that as an error. See also https://crbug.com/855722 BUG= 868028 Cq-Include-Trybots: luci.chromium.try:win_optional_gpu_tests_rel Change-Id: Icecd3ea8035ea783a625b11082e736d9609a15f8 Reviewed-on: https://chromium-review.googlesource.com/1153829 Reviewed-by: Brian Sheedy <bsheedy@chromium.org> Commit-Queue: Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#578851} [modify] https://crrev.com/b1471eca807da2c487f3fd775dd0232e0d9006c0/third_party/blink/renderer/modules/xr/xr_frame_provider.cc
,
Jul 30
Speculative fix seems to have worked, bot looks healthy(ish) again.
,
Jul 30
,
Jul 30
,
Aug 29
|
|||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||
Comment 1 by bsheedy@chromium.org
, Jul 26