1777528 - Crash in [@ mozilla::wr::RenderThread::SimulateDeviceReset]

Status: RESOLVED INACTIVE

(Core :: Graphics: WebRender, defect)

Description

[Gabriele Svelto [:gsvelto] (PTO)]

Crash report: https://crash-stats.mozilla.org/report/index/189ac446-a261-426a-9119-526f80220625

Reason: SIGSEGV / SEGV_MAPERR

Top 10 frames of crashing thread:

0 libxul.so mozilla::wr::RenderThread::SimulateDeviceReset gfx/webrender_bindings/RenderThread.cpp:987
1 libgobject-2.0.so.0 handlers_find gobject/gsignal.c:658
2 libgobject-2.0.so.0 signal_emit_unlocked_R gobject/gsignal.c:3743
3 libgobject-2.0.so.0 g_signal_emit_valist gobject/gsignal.c:3496
4 libgobject-2.0.so.0 g_signal_emit_by_name gobject/gsignal.c:3595
5 libgdk-3.so.0 gdk_x11_display_translate_event.lto_priv.0 /build/gtk+3.0-WfzL5N/gtk+3.0-3.24.33/gdk/x11/gdkdisplay-x11.c:1176
6 libgdk-3.so.0 _gdk_x11_event_translator_translate /build/gtk+3.0-WfzL5N/gtk+3.0-3.24.33/gdk/x11/gdkeventtranslator.c:51
7 libgdk-3.so.0 _gdk_x11_display_queue_events /build/gtk+3.0-WfzL5N/gtk+3.0-3.24.33/gdk/x11/gdkeventsource.c:341
8 libgdk-3.so.0 _gdk_x11_get_window_child_info /build/gtk+3.0-WfzL5N/gtk+3.0-3.24.33/gdk/x11/gdkasync.c:562
9 libgdk-3.so.0 gdk_event_source_dispatch /build/gtk+3.0-WfzL5N/gtk+3.0-3.24.33/gdk/x11/gdkeventsource.c:363

Just a handful of crashes but they're reliable. This is a shutdown crash where we try to post a runnable on an object which appears to be already NULL-ed out.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.

Comment 2

[Gabriele Svelto [:gsvelto] (PTO)]

This is a signature change caused by inlined functions, I need to improve this signature but in the meantime here's the new one.

Comment 3

[Gabriele Svelto [:gsvelto] (PTO)]

Note that the [@ mozilla::wr::RenderThread::AddRef] signature contains crashes unrelated to the one in comment 0. This is an example of the other crash, this one appears to be a NULL-pointer access but it might have been triggered by an OOM condition since all the reports have very low amounts of memory available.

Comment 4

[Gabriele Svelto [:gsvelto] (PTO)]

The second set of crashes will be split away from this bug once bug 1819065 lands.

Comment 5

[Glenn Watson [:gw]]

Given the volume and lack of repro steps, there is nothing we can do about this. Closing for now, but please reopen if volume or relevant information changes.