Closed
Bug 431916
Opened 17 years ago
Closed 14 years ago
FF grabs 100's MB of memory on link follow, reloads, etc.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: koppel, Unassigned)
Details
(Whiteboard: [CLOSEME 2010-07-30])
Attachments
(1 file)
136.80 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008050204 Minefield/3.0pre
Build Identifier: Gecko/2008050206 Minefield/3.0pre
On several occasions, starting with today's build, FF had high CPU usage and gobbled 100's of MB of memory, reaching a high of about 500 MB (reported by task manager). FF is usable after grabbing this memory. This has been triggered following a link, refreshing a page, and exiting (window close button).
Reproducible: Sometimes
Steps to Reproduce:
1. Click a link.
2.
3.
Actual Results:
High CPU, memory usage climbs by 100's of MB, but after about a minute page appears.
Expected Results:
Page appears within a second, much smaller increase in memory usage.
Reporter | ||
Comment 1•17 years ago
|
||
I currently have FF stopped in a debugger, there is deep recursion in js3250.dll, always through the same function. I'm going to try to get symbols and provide the function name.
Reporter | ||
Comment 2•17 years ago
|
||
The call below is part of the deep recursion, the entire stack trace is attached.
js3250.dll!MarkSharpObjects(JSContext * cx=0x093f0280, JSObject * obj=0x093f0280, JSIdArray * * idap=0x00000000) Line 412 + 0x10 bytes C
Reporter | ||
Comment 3•17 years ago
|
||
About that deep recursion, that only appeared at the beginning of an episode, not later on.
Reporter | ||
Comment 4•17 years ago
|
||
I get the following error when trying to close a tab:
too much recursion
nsSessionStore.js (line 1896)
The problem is also triggered when closing tabs and switching between tabs.
Reporter | ||
Comment 5•17 years ago
|
||
I have reliable STR. The problem occurs only with Firebug, so
I'm not sure if FF is to blame. I'll file a bug with Firebug too.
STR:
0. Start with fresh profile.
1. Install Firebug 1.1b12, restart.
2. In one tab visit http://cplusplus.com/reference/string/
3. In another tab visit http://www.opengl.org/registry/doc/glspec21.20061201.pdf
4. Exit, but have FF restore tabs so the two pages above will be restored.
5. Restart.
6. Focus a tab with the mouse and using arrows quickly switch back
and forth between the two tabs.
Firebug will show errors and tab switching will become sluggish
or freeze completely with high CPU usage and memory gobbling.
Firebug shows these errors:
urchinTracker is not defined
http://www.cplusplus.com/reference/string/
Line 124
[Exception... "Component is not available" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: file:///C:/Program%20Files/firefox/components/nsSessionStore.js :: sss_saveState :: line 1896" data: no]
[Break on this error] this._writeFile(this._sessionFile, oState.toSource());
too much recursion nsSessionStore.js (line 1896)
[Break on this error] this._writeFile(this._sessionFile, oState.toSource());
Reporter | ||
Comment 6•17 years ago
|
||
With Firebug 1.2a25X the high CPU usage and memory gobbling are gone. I still see errors such as:
[Exception... "Component is not available" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: file:///C:/Program%20Files/firefox/components/nsSessionStore.js :: sss_saveState :: line 1896" data: no]
file:///C:/Program%20Files/firefox/components/nsSessionStore.js
Line 1896
For the record, this is being tracked by Firebug bug http://code.google.com/p/fbug/issues/detail?id=617
Comment 7•14 years ago
|
||
Does this happen with firefox 3.6.6 or later in a fresh profile?
Whiteboard: [CLOSEME 2010-07-30]
Version: unspecified → 3.0 Branch
Comment 8•14 years ago
|
||
No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•