[Wayland] Gnome fractional scaling: Firefox crashes when dragging tabs: "cursor image size (64x64) not an integermultiple of scale (3)" + "Buffer size (340x228) must be an integer multiple of the buffer_scale (3)"
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox113 | --- | affected |
People
(Reporter: graham_alton, Unassigned)
References
(Blocks 3 open bugs)
Details
(Keywords: crash)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/113.0
Steps to reproduce:
Attempt to drag a tab to re-arrange the order of tabs or break a tab out into a separate window.
Firefox version 113.0-1.fc38.x86_64
Fedora Linux 38 with all latest updates as of 11th May 2023 (e.g. mutter-44.1-1, Wayland 1.22.0-1, NVidia proprietary drivers version 530.41.03, gnome-shell-44.1-1)
Actual results:
Firefox crashes immediately.
Expected results:
Tabs should be re-arranged or opened in a new window after the drag event finishes.
|
||
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•2 years ago
|
||
Can you please attach crash data?
https://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products#Using_local_debugging
Thanks.
|
Reporter | |
Comment 3•2 years ago
|
||
Argh, it's no longer crashing for me. I've started following the guide, however. Let me add more info in here if it starts happening again. Not sure if you prefer to close this and re-open or leave it open for a few days?
|
|
||
Comment 4•2 years ago
|
||
No problem, let's keep it open.
Thanks.
|
|
Reporter | |
Comment 5•2 years ago
|
||
I just started a new firefox window, went to re-arrange some tabs and got the crash again. Following the debugging guide, I run coredumpctl but I don't see any dumps from Firefox. Are there any other settings I might need to enable to have coredumps captured?
|
|
Reporter | |
Comment 6•2 years ago
|
||
Giving up with coredumpctl and running firefox through gdb seems to be a bit more fruitful.
I have several of these messages in GDB after the crash (I'm using Wayland with fractional scaling turned on)...
(firefox:82062): Gdk-WARNING **: 15:17:57.126: ../gdk/wayland/gdkcursor-wayland.c:242 cursor image size (64x64) not an integermultiple of scale (3)
I get one of these messages...
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Wayland protocol error: wl_surface@77: error 2: Buffer size (340x228) must be an integer multiple of the buffer_scale (3).
(t=40.1344) [GFX1-]: Wayland protocol error: wl_surface@77: error 2: Buffer size (340x228) must be an integer multiple of the buffer_scale (3).
Gdk-Message: 15:18:29.683: Error 71 (Protocol error) dispatching to Wayland display.
I also get these...
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=2Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=29.786) Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=1.9663) Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=32.4875) [GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
If the stack trace dump finishes, I'll upload that as well.
|
||
Updated•2 years ago
|
|
|
||
Comment 7•2 years ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:stransky, since the bug doesn't have a severity set, could you please set the severity or close the bug?
For more information, please visit BugBot documentation.
|
|
Reporter | |
Comment 8•2 years ago
|
||
Apologies, I hadn't realised this was waiting for more information from me... I'm happy to help but I might need some guidance on what information you're looking for.
|
|
||
Comment 9•2 years ago
|
||
It's known bug in Gtk cursor handling. No further info needed now. Thanks.
|
|
Reporter | |
Comment 10•2 years ago
|
||
Do you have a reference to a bug report for the Gtk cursor handling issue?
|
||
Comment 11•11 months ago
|
||
I can confirm this bug, crash report from my reproduction if needed : https://crash-stats.mozilla.org/report/index/6a159373-7be0-4935-be89-2daaf0240923#tab-details
|
|
||
Comment 12•11 months ago
|
||
We may implement our own cursor handling to fix various Gtk3/Wayland cursor bugs.
Description
•