FF105.0.2 is freezing w10, seemingly at random
Categories
(Core :: Widget: Win32, defect)
Tracking
()
People
(Reporter: email.seRiffle, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:105.0) Gecko/20100101 Firefox/105.0
Steps to reproduce:
It seems not to be readily reproducible;
The time to freeze of entire win10 desktop varies from a few(3) min to 20min;
I had open Amazon, gmail, and some readings from gmail.
Actual results:
The mouse at times works...
cannot access: w10.start menu, nor any other icon.
R-Click on desktop, does show proper dialog.
Had to, after 5min, hold POWER-OFF main button.
Expected results:
was working prior to update
|
||
Updated•3 years ago
|
|
||
Comment 1•3 years ago
|
||
Could you please try for a period of time to see if you could reproduce the freeze in safe mode. Here is a link that can help you do that:
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
Thanks.
|
Reporter | |
Comment 2•3 years ago
|
||
(In reply to Hani Yacoub from comment #1)
Could you please try for a period of time to see if you could reproduce the freeze in safe mode. Here is a link that can help you do that: https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
Thanks.
The link for safe-mode, didn't work'
I can only re-iterate that the combination must be in the afore mentioned sites opened.
When I did same with Chrome(latest, as of this date), I had no problem.
However, chrome does NOT have all the addOn's that FFox was using....
That therefore is the best, that I can tell you.
Today 10Oct2022, I have had no system freeze problems.
I had noticed that, at some point, via w10-Task-monitoring sw, that FF was using 700MB or RAM..
I have NOT been able to reproduce the problem, but, it has a profound impact (lockup), on system use.
I had to reboot, at least three times, via HW.PowerButton, as windows was unresponsive.
Several times, if I walked away from the laptop, the mouse was "seeable";
Sometimes, it was Clickable, on Start, or ToolBar, but nothing would happen.
At each failure, forced reboot, I first used FF.Settings.Check-for-update, but nothing new appeared.
You have access, to whatever dumps were done.
I'm afraid, al the above circumstancial evidence, is all that I have.
//end
|
|
Reporter | |
Comment 3•3 years ago
|
||
Today, possible link to freeze, but NOT as severe as prior report;
Was on website:
https://hopin.com/events/nodes-2022/registration?utm_campaign=eventcalendar&utm_source=website
Filled REGISTER button on that site;
Then tried to print the 'registration sucessful" page, using AddOn: Print Edit WE
[] I had attempted to select, all items that were NOT desired;
[] was only able to select ONE item, then FF.This page ONLY, froze, and could not recover. RAM was 955MB
[] I had to kill the pages, FF.Tab, to delete the Print Edit WE, application.
[] Once that was done, I was able to bring up the same webpage again, with no problems. RAM now 752MB
Unlike prior freezes, reported, The w10 interface itself, seemed NOT to be impacted. (That was a MUCH more serious issue).
I typically have at least 18 tabs concurrently open.
I also noted that the Print process (either Print Edit WE, OR the FF one), seem NOT to be running in seperate sub processes,
as I normaly find, I have to wait for 'printing' to terminate, for anything like proper performance..
Hope this helps alittle, although Not sure that this IS the entire cause...
Unless, some change to FF.latest, altered the API for AddOns...
For me, is Firefox 105.0.3. but it won't happen after downgraded to 105.0.2.
|
||
Comment 5•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Win32' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 6•3 years ago
|
||
Could you run mozregression to see when this started happening?
A number of Firefox versions will open in succession to narrow down when this started occurring. Simply answer "good" or "bad" based on whether or not a build reproduces the bug. Once finished, please post the output from the last run. It should give a last good and first bad revision as well as a link to look at the changesets in that range. Thank you!
(In reply to Stephen A Pohl [:spohl] from comment #6)
Could you run mozregression to see when this started happening?
A number of Firefox versions will open in succession to narrow down when this started occurring. Simply answer "good" or "bad" based on whether or not a build reproduces the bug. Once finished, please post the output from the last run. It should give a last good and first bad revision as well as a link to look at the changesets in that range. Thank you!
This bug seems disappear for a long time, now I using Firefox 107.0.1 without any problem, I think this bug had been disappear at least at firefox 106.
|
|
||
Comment 8•3 years ago
|
||
Thanks!
Description
•