"select" causes eventual browser crash due to memory consumption after large selection

RESOLVED EXPIRED

Status

()

RESOLVED EXPIRED
14 years ago
13 years ago

People

(Reporter: jdrogers, Assigned: blizzard)

Tracking

1.7 Branch
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050406 Firefox/1.0.2 (Debian package 1.0.2-3)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050406 Firefox/1.0.2 (Debian package 1.0.2-3)

Given a web page with a large (>~1mb) block of CSV formatted textual data in a
frame, upon selecting the data via a right-click "Select All", the firefox-bin
binary begins to consume memory relatively rapidly (1-5 mb/s) until all memory
is consumed and browser crashes.  The only way I have found to stop the
consumption is to close all instances of the browser.

Reproducible: Always

Steps to Reproduce:
1.  Open a web page with a large (>~1mb) block of CSV formated textual data in a
frame.
2.  Right click in the frame and choose "Select All".
3.  Watch memory resources as they will be consumed relatively quickly (1-5 mb/s)

Actual Results:  
Browser crashes after a couple of minutes.

Expected Results:  
Should not have consumed all of the memory (2gb or RAM).

Updated

14 years ago
Assignee: nobody → blizzard
Component: General → Widget: Gtk
Product: Firefox → Core
QA Contact: general → ian
Version: unspecified → 1.7 Branch

Comment 1

14 years ago
worksforme with linux suite trunk 2005050602.  Is there a testcase available
(you won't be able to attach it here)?
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.