785639 - Firefox crashes when loading very long web pages

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[t8av]

User Agent: Mozilla/5.0 (Windows NT 6.0; rv:14.0) Gecko/20100101 Firefox/14.0.1
Build ID: 20120713134347

Steps to reproduce:

I used Firefox to view a web page that is very long and contains a lot of images.


Actual results:

Firefox crashed.

(I also lost a very long and important download, but this should be a different bug - downloads should not stop when Firefox crashes).



Expected results:

Firefox should recognize web pages that consume a lot of memory and do one of the following:

1. Reduce (to minimum) the priority of the current process.

2. Assert a message that "this page is overloading system resources" and allow the user to stop the page loading.

Comment 1

[Scoobidiver (away)]

What is the URL?
Can you provide the crash ID from about:crashes?
Does it happen in Safe Mode (see https://support.mozilla.org/kb/troubleshoot-firefox-issues-using-safe-mode)?

Comment 2

[t8av]

The reason of this specific crash is not important. I did not add this bug/enhancement in order to get help debugging my browser and add-ons.

My point is that firefox can recognize in advance situations that may lead to crash, such as the very long web pages with many large images.

Maybe Firefox can also check available computer resources before reporting to the user it may going to crash.

The user should be given the option to terminate the current tab even if firefox is already  responding very slowly due to the overload.

Comment 3

[Andre Klapper]

t8av: We rather want to fix the root of the problem than adding workarounds. The application should "just work". Can you answer the questions in comment 1?

Comment 4

[t8av]

Sorry, I did not keep a record of the crash and the URL, and I do not remember it.

You can create by yourself an "overload situation" - just make a web page (can be local in your computer) with many large images (1MB up, each) and the crash will probably happen.

Comment 5

[Scoobidiver (away)]

(In reply to t8av from comment #4)
> You can create by yourself an "overload situation" - just make a web page
> (can be local in your computer) with many large images (1MB up, each) and
> the crash will probably happen.
Each OOM crash is different.