On macos, when wifi APs changes after waking up from sleep, FF gets stuck and not refreshes.
Categories
(Core :: Widget: Cocoa, defect)
Tracking
()
People
(Reporter: craigflambert, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:144.0) Gecko/20100101 Firefox/144.0
Steps to reproduce:
- Connect to Wifi AP at home. Then put Macbook into sleep.
- Go to another location and wake up the laptop. Connect to another Wifi AP.
Actual results:
FF is unresponsive. Opened pages are not updated / refreshed.
about:processes is not refreshed.
If I switched to another application and switch back, then the page is updated and FF becomes unresponsive again.
Expected results:
Pages should be refreshed automatically.
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Cocoa' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•1 year ago
|
||
Does this reproduce in a new profile and/or Troubleshoot Mode?
| Reporter | ||
Comment 3•1 year ago
|
||
I was able to reproduce this in Troubleshoot Mode. Do you still want me to try reproducing this in a new profile?
Comment 4•1 year ago
|
||
(In reply to craigflambert@gmail.com from comment #0)
If I switched to another application and switch back, then the page is updated and FF becomes unresponsive again.
Could you clarify this part? Do you mean to say that "Firefox becomes responsive again"? Or did you actually mean that it "becomes unresponsive again" after updating the page?
It would be good to know if this is a recent regression. Although this might be time consuming, would you be able to run mozregression? You can either choose to use the GUI tool, or simply run these three commands in a Terminal window:
sudo easy_install pip
sudo python3 -m pip install -U mozregression --ignore-installed
mozregression --good 2017-01-01
A number of Firefox versions will open in succession to narrow down when this started occurring. Simply type "good" or "bad" in Terminal 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!
Comment 5•1 year ago
|
||
Also: Are you connecting/disconnecting any external monitors by chance? If so, this might be related to bug 1985140.
Comment 6•1 year ago
|
||
Lastly, if you feel comfortable doing so, it would be great to get a profile when this is occurring. You can gather a profile using the following instructions:
https://profiler.firefox.com/docs/#/./async-posix-signal-control
Let me know if you need any assistance in capturing this profile. Thanks again!
| Reporter | ||
Comment 7•1 year ago
|
||
(In reply to Stephen A Pohl [:spohl] from comment #4)
(In reply to craigflambert@gmail.com from comment #0)
If I switched to another application and switch back, then the page is updated and FF becomes unresponsive again.
Could you clarify this part? Do you mean to say that "Firefox becomes responsive again"? Or did you actually mean that it "becomes unresponsive again" after updating the page?
It would be good to know if this is a recent regression. Although this might be time consuming, would you be able to run mozregression? You can either choose to use the GUI tool, or simply run these three commands in a Terminal window:
sudo easy_install pip sudo python3 -m pip install -U mozregression --ignore-installed mozregression --good 2017-01-01A number of Firefox versions will open in succession to narrow down when this started occurring. Simply type "good" or "bad" in Terminal 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!
I meant it "becomes unresponsive again" after updating the page.
I did connect / disconnect to an external monitor. Let me test according to bug 1985140 before checking regression. Thank you for pointing out that and getting a profile to me.
I don't know if my issue is related but I recently started experiencing Firefox freezing up after waking from MacOS sleep mode as well. I think this started happening within the past week. I'm currently running Firefox 145.0.1 (aarch64) on MacOS 15.7.1. I am, however, not switching WiFi APs.
| Reporter | ||
Comment 9•1 year ago
|
||
(In reply to [:Sam] from comment #8)
I don't know if my issue is related but I recently started experiencing Firefox freezing up after waking from MacOS sleep mode as well. I think this started happening within the past week. I'm currently running Firefox 145.0.1 (aarch64) on MacOS 15.7.1. I am, however, not switching WiFi APs.
I was able to confirm the issue was likely related to bug 1985140, but I could not mark this as a duplicate of that bug.
Comment 10•1 year ago
|
||
(In reply to craigflambert@gmail.com from comment #9)
(In reply to [:Sam] from comment #8)
I don't know if my issue is related but I recently started experiencing Firefox freezing up after waking from MacOS sleep mode as well. I think this started happening within the past week. I'm currently running Firefox 145.0.1 (aarch64) on MacOS 15.7.1. I am, however, not switching WiFi APs.
I was able to confirm the issue was likely related to bug 1985140, but I could not mark this as a duplicate of that bug.
Thanks! I just noticed the reference to that bug after I posted and I do think that my issue is related to the External Monitor bug you pointed out.
Updated•1 year ago
|
Description
•