Firefox 71 with Wayland crashes after called with parameter
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
People
(Reporter: office, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
22.95 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
-
Use Firefox on Sway with the Wayland backend enabled:
MOZ_ENABLE_WAYLAND=1
. -
On the command line make Firefox 71 open a URL or an image, for example:
firefox test_img.svg
. -
This will open the website or image fine in Firefox' window, but when switching to that window, Firefox crashes.
Actual results:
Firefox crashes. Here is a crash report that I filed: https://crash-stats.mozilla.org/report/index/d7caa966-c380-40dc-82ce-b4c0e0191209
Expected results:
Don't crash.
I can work around this issue two ways:
- Downgrade to Firefox 70.
- Use Firefox 71 but enable X11 as the window protocol instead of Wayland with
unset MOZ_ENABLE_WAYLAND
.
Reporter | ||
Comment 1•5 years ago
|
||
Reporter | ||
Comment 2•5 years ago
|
||
Here's the output of Firefox on the terminal after a crash:
(firefox:108321): Gdk-WARNING **: 11:08:09.182: (../gtk/gdk/wayland/gdkwindow-wayland.c:810):buffer_release_callback: runtime check failed: (impl->staging_cairo_surface != cairo_surface)
ExceptionHandler::GenerateDump cloned child 109643
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.
Comment 3•5 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
May be a dupe of Bug 1608029
Reporter | ||
Comment 5•5 years ago
|
||
I just upgraded to Firefox 73 and can confirm that this bug is fixed, thank you!
(In reply to Matthias Braun from comment #5)
I just upgraded to Firefox 73 and can confirm that this bug is fixed, thank you!
Thanks, but I'm not aware of any fix we did for that, I guess it's caused by system setup / state. Please reopen if you see it again.
Description
•