Closed Bug 1723940 Opened 3 years ago Closed 3 years ago

Crash in [@ mozilla::detail::MutexImpl::lock | mozilla::WaylandVsyncSource::WaylandDisplay::FrameCallback]

Categories

(Core :: Widget: Gtk, defect, P2)

Unspecified
Linux
defect

Tracking

()

RESOLVED FIXED
92 Branch
Tracking Status
firefox-esr78 --- unaffected
firefox-esr91 --- disabled
firefox90 --- disabled
firefox91 --- disabled
firefox92 --- fixed

People

(Reporter: gsvelto, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/2a2252f4-cb52-40fe-8c20-36e080210612

MOZ_CRASH Reason: MOZ_CRASH(mozilla::detail::MutexImpl::mutexLock: pthread_mutex_lock failed)

Top 10 frames of crashing thread:

0 firefox-bin mozilla::detail::MutexImpl::lock mozglue/misc/Mutex_posix.cpp:118
1 libxul.so mozilla::WaylandVsyncSource::WaylandDisplay::FrameCallback widget/gtk/WaylandVsyncSource.cpp:172
2 libxul.so mozilla::layers::CallbackMultiplexHelper::RunCallback gfx/layers/SurfacePoolWayland.cpp:44
3 libxul.so mozilla::detail::RunnableMethodImpl<mozilla::layers::CallbackMultiplexHelper*, void  xpcom/threads/nsThreadUtils.h:1203
4 libxul.so mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal xpcom/threads/TaskController.cpp:782
5 libxul.so nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1159
6 libxul.so mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:85
7 libxul.so MessageLoop::Run ipc/chromium/src/base/message_loop.cc:310
8 libxul.so nsBaseAppShell::Run widget/nsBaseAppShell.cpp:137
9 libxul.so nsAppStartup::Run toolkit/components/startup/nsAppStartup.cpp:273

Just a handful of crashes but they're coming from different user so this might be a real problem. It seems like we're failing to take this lock here. This shouldn't happen unless the lock has been destroyed or not initialized yet.

Severity: -- → S2
OS: Unspecified → Linux

Robert, any idea here?
Thanks.

Blocks: wayland
Flags: needinfo?(robert.mader)
Priority: -- → P2

This can only happen with gfx.webrender.compositor.force-enabled, thus blocking bug 1617498 instead. Lets see if it still happens after bug 1720375 landed, it changes a lot of that code.

Blocks: WR-linux-wayland-compositing
No longer blocks: wayland
Flags: needinfo?(robert.mader)

After bug 1718569 this backtrace can't happen any more, thus marking as fixed. We may see something similar, but enough code has changed that a new issue would be due.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.