Closed
Bug 628374
Opened 13 years ago
Closed 13 years ago
Memory leak: XUL's JS_sprintf_append leaks 4,88 KB of data
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
VERIFIED
INCOMPLETE
People
(Reporter: jan, Assigned: sfink)
References
Details
(Keywords: memory-leak, Whiteboard: [MemShrink:P2])
Attachments
(1 file)
2.91 KB,
text/plain
|
Details |
Memory leak: Process: firefox-bin Reponsible Library: XUL Responsible Frame: JS_sprintf_append Memory Addresses: See attachment Steps to reproduce: Start Firefox. Expected Result: Firefox shouldn't leak memory. Actual Result: Firefox leaks memory. User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b9) Gecko/20100101 Firefox/4.0b9
Updated•13 years ago
|
Whiteboard: leak
Comment 1•13 years ago
|
||
Need stack backtracing to get somewhere. /be
Comment 2•13 years ago
|
||
What tool created that attachment?
Comment 3•13 years ago
|
||
> What tool created that attachment? Instruments from Apple's Developer Tools I'd say. http://en.wikipedia.org/wiki/Instruments_%28application%29 It reports memory leaks for the JS_sprintf_append and JS_FindCompilationScope frames for me as well. Firefox 5.0.1.
Updated•13 years ago
|
Assignee: general → sphink
Whiteboard: [MemShrink] → [MemShrink:P2]
Comment 4•13 years ago
|
||
We looked at JS_sprintf_append and thought it didn't look suspicious. Maybe this report was produced using a build of Firefox without full native symbols, so the tool had to guess? It's suspicious that there isn't an offset from the symbol name. Small leak-through-shutdown bugs will soon be found by running Firefox under Valgrind regularly. See bug 631811.
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Reporter | ||
Updated•13 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•