搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Firefox crashes

  • 2 回覆
  • 2 有這個問題
  • 1 次檢視
  • 最近回覆由 cor-el

more options

I was on facebook and using the Graph search functionality. I kept scrolling the page, so I had a very big webpage downloaded. Eventually it crashed. I probably hit a limit on my system, or on memory, I'd like to know exactly what the limit was so I could look at solving it (more RAM or just allocate more disk memory etc.) Report ID: bp-f8f203bc-c4e5-4944-baf4-9b4c32140218

I was on facebook and using the Graph search functionality. I kept scrolling the page, so I had a very big webpage downloaded. Eventually it crashed. I probably hit a limit on my system, or on memory, I'd like to know exactly what the limit was so I could look at solving it (more RAM or just allocate more disk memory etc.) Report ID: bp-f8f203bc-c4e5-4944-baf4-9b4c32140218

所有回覆 (2)

more options

The crash report shows:

System Memory Use Percentage = 89

That's pretty high. I've seen crash reports with usage in the mid-90s, but I don't know where the cut-off is between healthy and unhealthy memory use, if there is a hard cut-off.

If you use any extensions that download or convert video in a page, that could be an issue with the FB news feed because there can be so many videos.

more options

The main issue with OOM crashes is usually memory fragmentation. You need a consistent block of free memory that is large enough to accommodate the requested size (OOM Allocation Size). In severe cases of fragmentation you can even get such an error with System Memory Use of in the 70%.

How much physical memory do you have?

You could try to increase the size of the page file (i.e. add an extra 1 GB) or install extra memory if you only have about 1 GB.