Closed Bug 1598995 Opened 4 years ago Closed 4 years ago

Firefox crash with Wayland: runtime check failed: (impl->staging_cairo_surface != cairo_surface)

Categories

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

71 Branch
Desktop
Linux
defect

Tracking

()

RESOLVED DUPLICATE of bug 1601082

People

(Reporter: bjonnh-ff, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, Whiteboard: [dupme?])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0

Steps to reproduce:

  • Open firefox (empty or used profile, no difference)
  • Open an URL from xdg or from a terminal (firefox-developer-edition https://www.mozilla.org)

Actual results:

Firefox Crashes and ask to restart. If I run firefox in a terminal I see:
(firefoxdeveloperedition:496386): Gdk-WARNING **: 21:58:25.007: (../gtk/gdk/wayland/gdkwindow-wayland.c:810):buffer_release_callback: runtime check failed: (impl->staging_cairo_surface != cairo_surface)
firefox: cairo-surface.c:930: cairo_surface_reference: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (&surface->ref_count)' failed.
ExceptionHandler::GenerateDump cloned child 496921
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.

Expected results:

Firefox should open a new tab

I tried with setting GDK_BACKEND=x11. As long as GDK_BACKEND is set for the new firefox call, when adding a new tab in a terminal it works.

If I set GDK_BACKEND only for the initial firefox call, the subsequent calls in another terminal with GDK_BACKEND unset do not open a new tab, and after a few seconds a window saying that firefox is not responding appears.

I will make firefox run in X11 mode for now. But I would be happy run any experiment that could help solve that issue.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core
OS: Unspecified → Linux
Hardware: Unspecified → Desktop

Which desktop do you run? And do you see it also with nightly and release?
Thanks.

Priority: -- → P2

I do not see it with release.
Desktop is gnome-shell.

Doesn't happen with 20191128-firefox-72.0a1 . So I guess it has been fixed and will make its way in the DE?

Isn't it expected to have some issues when meddling with GDK_BACKEND?

Wouldn't the use of MOZ_ENABLE_WAYLAND=1 solve the issue? Or Firefox really tries to support both approaches?

I only used GDK_BACKEND to revert to x11 (and then solving the issue). GDK_BACKEND was unset in the issue reported.

I can confirm this bug.

Archlinux (uptodate)
Mozilla Firefox 71.0

Same result with MOZ_ENABLE_WAYLAND=1 or GDK_BACKEND=wayland.

max@mde-oxalide % MOZ_ENABLE_WAYLAND=1  firefox
(firefox:2094): Gdk-WARNING **: 22:52:46.806: (../gtk/gdk/wayland/gdkwindow-wayland.c:810):buffer_release_callback: runtime check failed: (impl->staging_cairo_surface != cairo_surface)
firefox: cairo-surface.c:930: cairo_surface_reference: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (&surface->ref_count)' failed.
ExceptionHandler::GenerateDump cloned child 2328
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Failed to open curl lib from binary, use libcurl.so instead

the line Gdk-WARNING / crash appear when I run

xdg-open 'https://bugzilla.mozilla.org/show_bug.cgi?id=1598995'

Same result if I run MOZ_ENABLE_WAYLAND=1 firefox 'https://bugzilla.mozilla.org/show_bug.cgi?id=1598995'.

If I run firefox 'https://bugzilla.mozilla.org/show_bug.cgi?id=1598995' without env, it open a window saying:

Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.
Keywords: crash
Whiteboard: [dupme?]

I've started seeing this on Ubuntu with Firefox 71: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997. Firefox 70 did not suffer from this crash. I've stopped using MOZ_ENABLE_WAYLAND=1 as a workaround.

(In reply to Marius Gedminas from comment #9)

I've started seeing this on Ubuntu with Firefox 71: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997. Firefox 70 did not suffer from this crash. I've stopped using MOZ_ENABLE_WAYLAND=1 as a workaround.

Mariu, can you check if that works for you in Beta or Nightly?
Thanks.

Flags: needinfo?(marius)

I cannot reproduce this in Beta (firefox-72.0b4.tar.bz2).

Flags: needinfo?(marius)
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.