Closed Bug 1334932 Opened 7 years ago Closed 7 years ago

Intermittent TEST-UNEXPECTED-FAIL | file:///home/worker/workspace/build/tests/reftest/tests/layout/reftests/table-anonymous-boxes/infer-first-row.html | application terminated with exit code 11

Categories

(Core :: Graphics: WebRender, defect, P3)

54 Branch
x86_64
Linux
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox54 --- affected

People

(Reporter: kats, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [gfx-noted][gecko:UnobserveVsync])

https://treeherder.mozilla.org/logviewer.html#?job_id=72871748&repo=graphics&lineNumber=27785 for example. Has this stack which looks like it's specific to the webrender code.

 0  firefox!mozalloc_abort [mozalloc_abort.cpp:d52552ae7dcf : 33 + 0x5]
 1  firefox!abort [mozalloc_abort.cpp:d52552ae7dcf : 80 + 0x5]
 2  libnspr4.so!PR_Assert [prlog.c:d52552ae7dcf : 553 + 0x5]
 3  libnspr4.so!PR_Lock [ptsynch.c:d52552ae7dcf : 176 + 0x18]
 4  libxul.so!mozilla::OffTheBooksMutex::Lock [BlockingResourceBase.cpp:d52552ae7dcf : 382 + 0x9]
 5  libxul.so!mozilla::CompositorVsyncDispatcher::SetCompositorVsyncObserver [VsyncDispatcher.cpp:d52552ae7dcf : 74 + 0xb]
 6  libxul.so!mozilla::widget::InProcessX11CompositorWidget::ObserveVsync [InProcessX11CompositorWidget.cpp:d52552ae7dcf : 32 + 0x13]
 7  libxul.so!mozilla::layers::CompositorVsyncScheduler::UnobserveVsync [CompositorVsyncScheduler.cpp:d52552ae7dcf : 304 + 0xf]
 8  libxul.so!mozilla::layers::CompositorVsyncScheduler::Destroy [CompositorVsyncScheduler.cpp:d52552ae7dcf : 111 + 0x8]
 9  libxul.so!mozilla::layers::WebRenderBridgeParent::ClearResources [WebRenderBridgeParent.cpp:d52552ae7dcf : 726 + 0x5]
10  libxul.so!mozilla::layers::WebRenderBridgeParent::RecvShutdown [WebRenderBridgeParent.cpp:d52552ae7dcf : 164 + 0x5]
11  libxul.so!mozilla::layers::PWebRenderBridgeParent::OnMessageReceived [PWebRenderBridgeParent.cpp:d52552ae7dcf : 370 + 0xc]
See Also: → 1344951
Whiteboard: [gfx-noted] → [gfx-noted][gecko:UnobserveVsync]
Note that this happens on a variety of tests (the stack is mostly the same).
This seems to have gone away.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.