Closed
Bug 404895
Opened 17 years ago
Closed 17 years ago
Memory leak (10,000k/second) after loading an intranet asset search page, leads to computer lockup every time.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 404645
People
(Reporter: rom616, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b1) Gecko/2007110903 Firefox/3.0b1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b1) Gecko/2007110904 Firefox/3.0b1
Installed Firefox 3 beta 1 one this morning. I was testing it to see what applications worked on our intranet during pauses for processes to complete execution and some local workstation Apps to finish what they were doing. I discovered that whenever I opened a Remedy ticketing system asset search page, memory would immediately begin jumping by 10,000k/second. Required taskmanager to halt the process, but it had consumed 400,000K+ on a single open tab. This occurs every two or three times that I open the page.
The webpage is tagged as created by MS Frontpage 3.0, and runs using HTML (4, I believe), javascript, and a few java applets.
I can probably provide the source of the page, if that would help.
Reproducible: Sometimes
Steps to Reproduce:
1. Open Firefox 3 beta 1 (need to be using normal work-day programs as well)
2. Click on the link to the webpage.
3. Watch taskmanager for the firefox process memory to spike, almost immediately.
Actual Results:
Computer became very slow, memory usage for Firefox 3 beta 1 reached around 400,000K before taskmanager could kill the process. Until the computer was rebooted, everything ran very slowly after Firefox's run on memory.
Expected Results:
Opened the page and left memory usage at normal levels (seems to be about 45,000k -60,000k for other pages)
Comment 1•17 years ago
|
||
Does it stop happening if you go
Edit > Preferences > Security > Uncheck "Tell me if the site I'm visiting is
a suspected forgery"
If so, this is a dupe of bug 404645.
I'll check it after Thanksgiving and report back.
Thanks for the quick reply!
I have not received any more of the memory leaks following the disabling of the "suspected forgery" option.
Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•