1798050 - FF 106.0.2 freezes on every page containing video

Status: RESOLVED DUPLICATE of bug 1798099

(Core :: Audio/Video: Playback, defect)

Description

[[:ColourGrey]]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:106.0) Gecko/20100101 Firefox/106.0

Steps to reproduce:

Visit any page containing video, for instance:
https://www.youtube.com/watch?v=wqaFYeZ6D3o
https://arstechnica.com/tech-policy/2022/10/elon-musk-completes-twitter-purchase-immediately-fires-ceo-and-other-execs/

Actual results:

FF becomes unresponsive and needs to be closed by force. This does not happen in troubleshoot mode, but it does happen with newly created, unaltered profiles. Also, refreshing FF did not help. So this bug is not caused by extensions or user settings, it is much deeper.
This seems to happen only since 106.0.2 (or possibly 106.0.1), I am sure that it was not present in 106.
Windows 10 Home 21H2, OS build 19044.2130, 64 bit.
System: Yoga Slim 7 14ARE05, AMD Ryzen 5 4500U with Radeon Graphics.

Comment 1

[[:ColourGrey]]

Unchecking "Use recommended performance settings" and then unchecking "Use hardware acceleration when available" does not solve the problem, the bug persists.

Comment 2

[[:ColourGrey]]

1. The bug cannot probably be caused by driver updates because the latest update of my system happened 3 weeks ago, while this bug is 2-3 days old.

2. The bug manifests itself randomly: yesterday and today the first attempts of the day to view video content froze FF, but after several attempts everything returned to working fine without me doing anything in particular.

Comment 3

[Jeff Muizelaar [:jrmuizel]]

The next time it happens can you use https://github.com/b0bh00d/crash-firefox to kill Firefox. That should hopefully create a crash report that you can see in about:crashes. Make sure the crash report is submitted and please share the URL from the "view" link.

Comment 4

[[:ColourGrey]]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #3)

The next time it happens can you use https://github.com/b0bh00d/crash-firefox to kill Firefox. That should hopefully create a crash report that you can see in about:crashes. Make sure the crash report is submitted and please share the URL from the "view" link.

I have tried to do so: that program does make FF crash, but no crash report is generated!

Comment 5

[Jeff Muizelaar [:jrmuizel]]

Does Firefox just disappear without showing anything?

Comment 6

[Justin Peter]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #5)

Does Firefox just disappear without showing anything?

Yes. Per https://github.com/bsmedberg/crashfirefox-intentionally this utility defaults to the most recently created process, and per bug 1600145 this no longer works for content processes. It works for the parent process, and maybe (cf. bug 1798099) the GPU process.

Comment 7

[[:ColourGrey]]

Attachment: about-support-raw.json

This is the output of about:support.

Comment 8

[Jeff Muizelaar [:jrmuizel]]

empty.internet.persona, there's a new version of crash-firefox available: https://github.com/b0bh00d/crash-firefox/releases/tag/Windows-64-1.1
This version allows killing the GPU process by selecting firefox.exe.gpu (highlighed in green) from the process drop down. Can you try killing that the next time this happens and checking if that gives you a crash report in about:crashes?

Comment 9

[[:ColourGrey]]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #8)

empty.internet.persona, there's a new version of crash-firefox available: https://github.com/b0bh00d/crash-firefox/releases/tag/Windows-64-1.1
This version allows killing the GPU process by selecting firefox.exe.gpu (highlighed in green) from the process drop down. Can you try killing that the next time this happens and checking if that gives you a crash report in about:crashes?

I do want to help, but how? Whenever I zap the firefox.exe.gpu process, the corresponding FF window goes completely white for a few seconds, then the process is restarted and... about:crashes is empty. Are these crash reports saved in some location that I do not know of?

Comment 10

[Jeff Muizelaar [:jrmuizel]]

(In reply to empty.internet.persona from comment #9)

I do want to help, but how? Whenever I zap the firefox.exe.gpu process, the corresponding FF window goes completely white for a few seconds, then the process is restarted and... about:crashes is empty. Are these crash reports saved in some location that I do not know of?

Weird. What happens if you try to zap firefox.exe.gpu when Firefox is not hung? Does it generate a crash report then?

Comment 11

[[:ColourGrey]]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #10)

I do want to help, but how? Whenever I zap the firefox.exe.gpu process, the corresponding FF window goes completely white for a few seconds, then the process is restarted and... about:crashes is empty. Are these crash reports saved in some location that I do not know of?

Weird. What happens if you try to zap firefox.exe.gpu when Firefox is not hung? Does it generate a crash report then?

No, it does not. And I am not the only one not seeing crash reports: https://www.reddit.com/r/firefox/comments/yfkplj/comment/iu50kzl/?utm_source=reddit&utm_medium=web2x&context=3. I believe that this just exhibits one more FF bug, namely that crashes are not taken care of as they should.

Comment 12

[Bob Hood [:bhood]]

New release of crash-firefox which uses NtDll::DbgBreakPoint as the entry point for the thread instead of 0x0. Please give it a try.

https://github.com/b0bh00d/crash-firefox/releases/tag/Windows-64-1.2

Comment 13

[[:ColourGrey]]

(In reply to Bob Hood [:bhood] from comment #12)

New release of crash-firefox which uses NtDll::DbgBreakPoint as the entry point for the thread instead of 0x0. Please give it a try.

https://github.com/b0bh00d/crash-firefox/releases/tag/Windows-64-1.2

I shall, but currently FF 106.0.3 no longer wants to freeze. If this minor FF update fixes my problem, I shall probably install 106.0.2 in parallel in order to further explore this bug, so please do not close this bug report yet.

Comment 14

[Jim Mathies [:jimm]]

could be a dupe of bug 1798099.