Repeated Mac Mini Crashes while running Firefox 72-- Memory Pressure?
Categories
(Core :: Memory Allocator, defect)
Tracking
()
People
(Reporter: erwinm, Unassigned)
Details
(Keywords: memory-footprint)
Attachments
(2 files)
Screen Shot 2020-02-05 at 3.33.58 PM.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
I switched to Firefox 72.
I ran Firefox 72, as well as more demanding tools-- such as Steam, k2pdfopt, or Disk Utility.
Actual results:
Firefox 72 + any of these demanding tools can sometimes crash my Mac Mini. Not always, but 3 times in the last 3 days.
Expected results:
Waterfox Classic + any of these demanding tools would rarely crash my Mac Mini.
I was checking with Bresink's System Monitor, and memory maxxed out before my last crash. I also checked with System Monitor after my computer rebooted, and Firefox seems to use a ton of memory.
I can't rule out hardware issues right now, and Apple's diagnostics partition isn't accessible with my disabilities.
I can't try Safe Mode with my disabilities, it's not safe.
Note that I've got 8 GB of RAM, so this is less than 1/4 the total. But Firefox accounts for several of the most demanding processes at any given time.
Related: Bug 1595627
If you reduce the number of content processes you're running, do you crash less?
You can adjust that using these instructions: https://support.mozilla.org/en-US/kb/performance-settings
I don't know. I've been keeping an eye on memory usage, but I'll try that.
No more crashes while watching memory usage. However it's currently running about 1.9 GB for 4 tabs with 4 processes.
|
||
Comment 7•6 years ago
|
||
I also attempted reproducing your issue on a MacMini (mid 2011) with 6 GB of RAM but I couldn't make it crash with Firefox Release v72.0.2.
This is what I did:
- Opened browser.
- Open a bunch of other applications to attempt to fill RAM memory.
- Open a bunch of websites that use a lot of memory in an attempt to fill as much as possible.
Notice: The browser or the MAC device did not crash ar make any unexpected issues after filling as much as 5.5 GB/6 Gb of ram. Furthermore, I find it very hard to fill the last 0.5 GB of memory.
To attempt troubleshooting this bug, I would like to ask you some questions:
- Did you mean to say that the MacMini crashed, not the Firefox Browser. Is that right?
- If yes, what exactly makes you believe that this might be a Firefox issue and not a MacMini issue?
- Which model of MacMini do you have?
- What Mac OS version is it using?
- I think that a Firefox memory report would most likely explain the issue in this case, so I would like to ask you to capture a memory report while attempting to reproduce the same issue as before. Will you do this for us?
The information needed is here: https://developer.mozilla.org/en-US/docs/Mozilla/Performance/about:memory
So it would be best if you would try to open the same applications as before, but keep an eye on the system memory so it doesn't crash before you can capture the memory report. Please attach the memory report to this bug.
Thank you for your contribution!
-
Yes, the Mac crashed.
-
I think it's both, because there were a lot more crashes after switching from WF to FF. Going from about 1/month to 1/day.
-
2018 Mac Mini with 8 GB of RAM and 128 GB internal SSD. Running from a 500 GB external drive via USB-C, because of space limitations and Migration Assistant bugs.
-
Mojave 10.12.6
-
I can't read the results because of scrolling bugs, but I'll try to attach them.
|
|
||
Comment 10•6 years ago
|
||
I hope this helps, otherwise, whoever gets to triage this, please provide an opinion on how this should be troubleshot. Thank you!
|
||
Comment 11•6 years ago
|
||
The priority flag is not set for this bug.
:glandium, could you have a look please?
For more information, please visit auto_nag documentation.
|
Reporter | |
Comment 12•6 years ago
|
||
Still no more crashes at 4 processes.
|
||
Updated•6 years ago
|
Description
•