Closed
Bug 611325
Opened 14 years ago
Closed 14 years ago
valgrind detects leak under JS_GetStringBytes
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: sayrer, Assigned: igor)
Details
Attachments
(4 files)
we've recently changed this a lot. assigning to igor.
|
Reporter | |
Updated•14 years ago
|
Assignee: general → igor
|
|
Reporter | |
Updated•14 years ago
|
blocking2.0: --- → beta8+
|
|
Reporter | |
Comment 1•14 years ago
|
||
igor, this blocks b8.
|
|
Reporter | |
Updated•14 years ago
|
OS: Windows CE → Linux
|
|
Reporter | |
Comment 2•14 years ago
|
||
|
|
Reporter | |
Comment 3•14 years ago
|
||
Igor says on IRC that this is probably fixed by bug 610198.
|
Assignee | |
Comment 4•14 years ago
|
||
The bug 610198 indeed removes the affected usage of JS_GetStringBytes but the I will check the code in any case as some code paths in DeflateStringToBytes may leak indeed.
|
|
Reporter | |
Comment 5•14 years ago
|
||
|
|
Reporter | |
Comment 6•14 years ago
|
||
This patch prints out which strings were added but never removed. They are all interface and function names. This jives with the stacks valgrind gives. Always under either XPCConvert::JSData2Native or XPCJSStackFrame::CreateStack -> JS_GetFunctionName.
|
|
Reporter | |
Comment 7•14 years ago
|
||
leaked 168 strings stopping / starting the browser. I'll see if I can get this number to go up by surfing for a long time.
|
|
Reporter | |
Updated•14 years ago
|
blocking2.0: beta8+ → ---
OS: Linux → Windows CE
|
|
Reporter | |
Comment 8•14 years ago
|
||
fixed by 610198
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•