Closed
Bug 761893
Opened 12 years ago
Closed 12 years ago
GC never seems to trigger to collect all the strings being allocated in this testcase
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: bzbarsky, Unassigned)
Details
(Whiteboard: [js:p2][js:bumped:2][js:ni])
Attachments
(1 file)
1.23 KB,
text/html
|
Details |
See attached testcase. If I run it for a bit, I get memory growth by tens to hundreds of megabytes. If I then open about:memory, it's showing as all being string-chars from the compartment of the testcase. As soon as I trigger a GC (eg. reload about:memory a few times) it all goes away.
Updated•12 years ago
|
Whiteboard: [js:p2:fx16]
Updated•12 years ago
|
Whiteboard: [js:p2:fx16] → [js:p2:fx17][js:bumped:1]
Updated•12 years ago
|
Whiteboard: [js:p2:fx17][js:bumped:1] → [js:p2:fx18][js:bumped:2]
Updated•12 years ago
|
Whiteboard: [js:p2:fx18][js:bumped:2] → [js:p2][js:bumped:2][js:ni]
I let this run overnight and memory usage seemed pretty stable. Is this still a problem, Boris?
Reporter | ||
Comment 2•12 years ago
|
||
Seems to be ok now.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•