Closed Bug 1609910 Opened 5 years ago Closed 5 years ago

Changing full-screen-api.transition-duration.leave to 0 0 in about:config causes Firefox to freeze when exiting full screen video.

Categories

(Firefox :: Untriaged, defect)

72 Branch
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: world1.a, Unassigned, NeedInfo)

Details

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

Steps to reproduce:

After updating to 72.0.1 I noticed that when I try to exit from a video which is in full screen, Firefox would freeze. It usually doesn't happen on the "first exit" to original mode but definitely after second or third.

Actual results:

My settings in about:config regarding full screen warning and transition, were all set to 0 or 00 for the last couple of years. After this issue started occurring, I started toggling each setting and I noticed that full-screen-api.transition-duration.leave was the culprit. All other settings were left at 0. Exiting video from full screen does not freeze on exit only if full-screen-api.transition-duration.leave is set to 1 1 or higher. Zero and anything lower, causes the whole computer to freeze. Task manager or any windows shortcuts do not appear and the only solution is to physically force shut down the computer. I tested this on two different computers both running latest version of Windows 10.

Expected results:

I tried installing a new Firefox beta version with new profile, disabled hardware acceleration etc. but as soon as I changed above mentioned settings, it started freezing again. I hope that this can be solved in future versions.

I failed to reproduce your bug on the current release version of Firefox (72) and Firefox Beta (73). full-screen-api.transition-duration.leave was set to 0 0 and I tried to trigger it by fullscreening random videos on Youtube.

All other settings were left at 0

Do you mean all the other full-screen-api prefs are set to 0 in you profile? Could you report the exact options that are set when this problem occurs? How does your browser behave if only full-screen-api.transition-duration.leave is 0 0 and all the other settings are at their factory default?

Flags: needinfo?(world1.a)

Did you try to exit full screen few times (I usually use Esc) and still didn't have an issue? My current settings that do not cause the issue:

full-screen-api.transition-duration.enter 0 0
full-screen-api.transition-duration.leave 1 1
full-screen-api.transition.timeout 0
full-screen-api.unprefix.enabled true
full-screen-api.warning.delay -1
full-screen-api.warning.timeout -1

When I leave everything else as it is above and change full-screen-api.transition-duration.leave to 0 0 that's when the screen/computer freezes.

When all other settings are at their factory default and full-screen-api.transition-duration.leave is 0 0 everything is fine.

Flags: needinfo?(world1.a)

I tried to reproduce your issue again with the provided settings and full-screen-api.transition-duration.leave set to 0 0. However, I can't produce any freezes on either Windows or Linux.

Did you try to exit full screen few times (I usually use Esc) and still didn't have an issue?

Yes, i did exactly that.

No real idea what causes this for you. It might be interesting to try if this still occurs if full-screen-api.warning.delay -1 and full-screen-api.warning.timeout -1 are both set to zero. Negative timings are pretty nonsensical and maybe this breaks something?

(In reply to Jan Sonntag from comment #3)

I tried to reproduce your issue again with the provided settings and full-screen-api.transition-duration.leave set to 0 0. However, I can't produce any freezes on either Windows or Linux.

Did you try to exit full screen few times (I usually use Esc) and still didn't have an issue?

Yes, i did exactly that.

No real idea what causes this for you. It might be interesting to try if this still occurs if full-screen-api.warning.delay -1 and full-screen-api.warning.timeout -1 are both set to zero. Negative timings are pretty nonsensical and maybe this breaks something?

I created an account to report the same issue. I refreshed Firefox, readded the addons one by one, and eventually figured out it's to do with the full-screen-api.warning.delay. It does not happen on YouTube, in my experience only p*rn sites (eg xvideos.com)

Windows 10 freezes, even ctrl+alt+del won't work, though the mouse cursor can move around. Cutting the power is the only solution. I hope that helps with reproducing the bug, and apologies for being so blunt about which websites cause it.

(In reply to michelle_o52 from comment #4)

(In reply to Jan Sonntag from comment #3)

I tried to reproduce your issue again with the provided settings and full-screen-api.transition-duration.leave set to 0 0. However, I can't produce any freezes on either Windows or Linux.

Did you try to exit full screen few times (I usually use Esc) and still didn't have an issue?

Yes, i did exactly that.

No real idea what causes this for you. It might be interesting to try if this still occurs if full-screen-api.warning.delay -1 and full-screen-api.warning.timeout -1 are both set to zero. Negative timings are pretty nonsensical and maybe this breaks something?

I created an account to report the same issue. I refreshed Firefox, readded the addons one by one, and eventually figured out it's to do with the full-screen-api.warning.delay. It does not happen on YouTube, in my experience only p*rn sites (eg xvideos.com)

Windows 10 freezes, even ctrl+alt+del won't work, though the mouse cursor can move around. Cutting the power is the only solution. I hope that helps with reproducing the bug, and apologies for being so blunt about which websites cause it.

Don't worry about being blunt :) With me it happens on many websites. With YouTube it takes few exists before it freezes but many times after the first try. Aside from my two computers that I mentioned in the beginning, I also tried to reproduce the bug on some of my friends computers and their computer froze like mine did. I am also glad that you wrote as well to confirm.

I also couldn't reproduce this issue on Windows 10 x 64 using Firefox 72.0.1 and Firefox 73 beta 7.

World1.a, could you please attach here the information from about:support page?

Flags: needinfo?(world1.a)

Closing as Resolved: Incomplete due to no update from the reporter.
World1.a, please feel free to reopen it if you still have the problem reproducible (on the latest release) and you can provide additional details that could help us reproduce or identify your issue. Thanks!

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.