Closed
Bug 4288
Opened 26 years ago
Closed 26 years ago
MLK: nsWebShell leaking a nsJSContext?
Categories
(Core :: XUL, defect, P1)
Tracking
()
M5
People
(Reporter: bruce, Assigned: nisheeth_mozilla)
Details
Pull and build from March 24, 1999. Solaris 2.6, gcc 2.7.x. This is from just a
startup and shutdown of apprunner.
MLK: 1272 bytes leaked in 53 blocks
* This memory was allocated from:
malloc [rtlib.o]
js_alloc_atom [jsatom.c:154]
JS_HashTableRawAdd [jshash.c:224]
js_AtomizeString [jsatom.c:492]
js_Atomize [jsatom.c:524]
js_InitScanner [jsscan.c:149]
js_NewContext [jscntxt.c:59]
JS_NewContext [jsapi.c:567]
nsJSContext::nsJSContext(JSRuntime*) [nsJSEnvironment.cpp:91]
nsJSEnvironment::GetNewContext() [nsJSEnvironment.cpp:401]
NS_CreateContext [nsJSEnvironment.cpp:409]
nsWebShell::CreateScriptEnvironment() [nsWebShell.cpp:2019]
nsWebShell::GetScriptGlobalObject(nsIScriptGlobalObject**) [nsWebShell.c
pp:2047]
DocumentViewerImpl::Init(void*,nsIDeviceContext*,nsIPref*,const nsRect&,
nsScrollPreference) [nsDocumentViewer.cpp:314]
nsWebShell::Embed(nsIContentViewer*,const char*,nsISupports*) [nsWebShel
l.cpp:681]
nsDocumentBindInfo::OnStartBinding(nsIURL*,const char*) [nsDocLoader.cpp
:1716]
Updated•26 years ago
|
Assignee: trudelle → nisheeth
Comment 1•26 years ago
|
||
reassigning to nisheeth, since Pink thinks he owns it now.
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•26 years ago
|
Target Milestone: M4
Assignee | ||
Comment 2•26 years ago
|
||
Accepting bug...
Assignee | ||
Comment 3•26 years ago
|
||
Setting milestone to M4...
Assignee | ||
Updated•26 years ago
|
Priority: P3 → P1
Assignee | ||
Comment 4•26 years ago
|
||
Setting priority to P1...
Comment 5•26 years ago
|
||
Is this the same as bug 4127? If so, then it seems to be caused by menu items.
Assignee | ||
Updated•26 years ago
|
Target Milestone: M4 → M5
Assignee | ||
Comment 6•26 years ago
|
||
Moving bug to M5...
Comment 7•26 years ago
|
||
I have the changes ready that make menu items behave better, but I don't know if
this solves all the refcount problems (doubt it). Hopefully the tree will open
soon.
Assignee | ||
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•