Closed
Bug 307917
Opened 19 years ago
Closed 17 years ago
Arbitrarily long pages exhaust memory
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: mlemos, Unassigned)
Details
(Whiteboard: CLOSEME 06/27)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050715 Firefox/1.0.6 SUSE/1.0.6-4 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050715 Firefox/1.0.6 SUSE/1.0.6-4 Accidentally I wrote a script that generates a very long page with debug information of a Web application. Firefox exhausted the browser machine memory and I had to kill it before the system became unusable. It seems to me that any malicious site can crash the user machine just by serving an arbitrarily long page. Shouldn't there be a protection to prevent that Firefox exhausts the system memory? Maybe there should be a limit option that stop loading pages when the available system memory is below some threshold. Reproducible: Always
Comment 1•19 years ago
|
||
I think this "bug" is more of a general design issue than a firefox bug specefically, i know it has happened to me with other browsers too. A memory limit option would probably be the best solution, either stop loading the page or automatically close the program.
Mozilla/5.0 (Windows; U; Win98; fr-FR; rv:1.7.12) Gecko/20060116 - Build ID: null I've found a good example to illustrate this problem : just try to load ftp://ftp.debian.org/debian/dists/stable/Contents-i386.gz and wait for your system to crash ;(
Comment 4•18 years ago
|
||
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 06/27
Version: unspecified → 1.0 Branch
Comment 5•17 years ago
|
||
Comment 3 is covered in other bugs. We need a valid testcase to determine exactly where Firefox is misusing memory. I'm closing this bug as INCOMPLETE until the reporter produces the page which he was talking about in comment 0.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•