When an external screen is connected to the computer, opening a video in full screen on that external screen makes firefox crash
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: anoh.erwin05, Unassigned, NeedInfo)
References
(Blocks 2 open bugs)
Details
(Keywords: crash)
Crash Data
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:157.0) Gecko/20100101 Firefox/157.0
Steps to reproduce
- Connect an additional monitor to the computer: in my example, I have my main monitor and an Amazon FIreTV as second monitor
- open a website that streams videos in the second monitor: in my example I opened youtube.com
- switch to full screen
Actual results
The Firefox window/process immediately crashed. This also happened with other websites and did not happen on Chromium for example.
Expected results
The video should be in full screen without making firefox crash.
An other important consideration is that: minutes ago, I upgraded my Ubuntu from 24 to 26. I never had that issue on Ubuntu 24 and I always encounter the issue in 26. I switched to Ubuntu 26 on October 9th. Also, note the screen type : a smart TV, and the screen resolution 4k which is higher than my main screen 2k.
Comment 1•1 month ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, but is not confident enough to move the bug to that component.
Comment 2•1 month ago
|
||
Can you submit the crash report if you haven't already, and then go to about:crashes, and copy-paste the link to the crash on crash-stats.mozilla.org here? That will allow us to see what part of the code is crashing so the right people can take a look.
(Taking a wild stab at a more appropriate component but really, we will likely need the crash information to do more here, unless this is crashing for everyone on Linux with two screens, which seems somewhat unlikely - unfortunately I do not have a setup to be able to attempt to reproduce)
| Reporter | ||
Comment 3•1 month ago
|
||
here is the most crash report I sent: https://crash-stats.mozilla.org/report/index/bc6b8e91-2e1d-44b6-a7e7-7826a0261014
Comment 4•1 month ago
|
||
(In reply to Ervin Anoh from comment #3)
here is the most crash report I sent: https://crash-stats.mozilla.org/report/index/bc6b8e91-2e1d-44b6-a7e7-7826a0261014
Thank you! This looks like it is in gtk/wayland code. It's previously been filed as bug 2035750 but this bug has STR which are usually useful so I'll avoid duplicating it over for now. :stransky, is there other information that would help work out a root cause here and fix it?
Updated•1 month ago
|
Comment 5•1 month ago
|
||
Thanks for the crash report and the steps to reproduce. Could you try one thing for me?
- Type
about:configin the address bar and accept the warning. - Search for
media.ffmpeg.vaapi.enabledand click the toggle button so it showsfalse. - Restart Firefox, then put a video in full screen on the TV again.
Does it still crash? If it doesn't, you can keep that setting as a workaround for now. It tells me which part of Firefox is failing.
Comment 6•1 month ago
|
||
(ubuntu:gnome) [destroyed object]: error 7: failed to import supplied dmabufs: Could not bind the given EGLImage to a CoglTexture2D
Proxy: WP:E WP:CA WP:CPCA
that comes from EGLImage dmabuf import code, so won't be reproducible without VA-API (or Vulkan).
Ervin, please run on terminal with MOZ_LOG="Dmabuf:5" env variable, make it crash and attach the log here, for instance as:
MOZ_LOG="Dmabuf:5" firefox > log.txt 2>&1
Thanks.
Comment 7•1 month ago
|
||
The bug has a crash signature, thus the bug will be considered confirmed.
Updated•1 month ago
|
| Reporter | ||
Comment 8•1 month ago
|
||
(In reply to Thinker Li [:sinker] from comment #5)
Thanks for the crash report and the steps to reproduce. Could you try one thing for me?
- Type
about:configin the address bar and accept the warning.- Search for
media.ffmpeg.vaapi.enabledand click the toggle button so it showsfalse.- Restart Firefox, then put a video in full screen on the TV again.
Does it still crash? If it doesn't, you can keep that setting as a workaround for now. It tells me which part of Firefox is failing.
I just tried and this solution did not work
| Reporter | ||
Comment 9•1 month ago
|
||
| Reporter | ||
Comment 10•1 month ago
|
||
(In reply to Martin Stránský [:stransky] (ni? me) from comment #6)
(ubuntu:gnome) [destroyed object]: error 7: failed to import supplied dmabufs: Could not bind the given EGLImage to a CoglTexture2D Proxy: WP:E WP:CA WP:CPCAthat comes from EGLImage dmabuf import code, so won't be reproducible without VA-API (or Vulkan).
Ervin, please run on terminal with MOZ_LOG="Dmabuf:5" env variable, make it crash and attach the log here, for instance as:
MOZ_LOG="Dmabuf:5" firefox > log.txt 2>&1Thanks.
Please find attached log.txt file I got after runing the command you sent.
Comment 11•1 month ago
|
||
It looks like the message is comming from MESA GL library and not from Firefox itself. Firefox doesn't create and dmabuf - SW playback is used.
Please attach your about:support page.
Thanks.
Description
•