搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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.