Closed Bug 296752 Opened 20 years ago Closed 20 years ago

memory crash if you use firefox to test your web pages like i do all day long

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: eaglesoft, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Firefox will not load all the time but will not clear it's self from memory so you have to do a ctrl+alt+delete then clear Firefox from memory and start it again I have to do this about 50 to 75 times a day as I work on my web page all day long. Making changes and use Firefox to test my pages I load it through my text editor TextPad v4.7.3 best HTML editor I have ever seen I call up Firefox through TextPad as it just passes the HTML page to Firefox. I know this is not a big problem but it does happen too much I think and should be looked into, I talked to the Author of TextPad and he told me that TextPad only pass information to the default web browser and nothing else. Reproducible: Sometimes Steps to Reproduce: 1.First you would need text/html editor that passes html to Firefox 2.Edit some html pages and it will happen - Firefox will not load 3.Then you will have to hit ctrl+alt=delete to stop process and take out Firefox and restart Firefox Actual Results: Firefox works fine till it fails to dump memory and you have to do the ctrl+alt=delete and STOP or take Firefox out of memory Expected Results: After loading and when it is STOPed it should it NOT dump it's memory back to system ? I would think so ?
Does this seem like any of the following? bug 130157, bug 249469, bug 281824? There *are* memory leaks in the Core (Mozilla) which is why FF also has memory leaks. While we try our best to plug these leaks, there are some like this that seem to have no source other than simple "browsing" like this one. Anyone want to take a stab at which bug to make this a dupe of?
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
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.