Closed
Bug 14170
Opened 26 years ago
Closed 26 years ago
OJI causes service manager leak
Categories
(Core Graveyard :: Java: OJI, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
M11
People
(Reporter: vidur, Assigned: edburns)
References
Details
Attachments
(1 file)
|
4.97 KB,
patch
|
Details | Diff | Splinter Review |
It seems that the NSGetFactory for the OJI DLL maintains a reference to the
service manager
(http://lxr.mozilla.org/seamonkey/source/modules/oji/src/nsCJVMManagerFactory.cp
p#112) but never releases it. The resulting service manager leak results in many
more downstream leaks.
| Reporter | ||
Updated•26 years ago
|
Priority: P3 → P1
*** Bug 8178 has been marked as a duplicate of this bug. ***
Hmm... I don't understand why we need to cache a global reference to the service
manager. It is only used in one method, NSGetFactory().
| Reporter | ||
Comment 3•26 years ago
|
||
Actually, it's used in other files in the same module (see JVM_GetJVMMgr(), for
example).
How do I obtain a reference to the ServiceManager on demand? There is no case
when I can release it so I could implement a strategy where I just re-obtain
and release it every time I need to use it. Can I just save the
nsIServiceManager reference I receive from NSGetFactory()?
Instead of asking for the ServiceManager and invoking methods from it, why
can't I just use nsServiceManeger static methods, as is done in all the files
returned in the query
http://lxr.mozilla.org/mozilla/search?string=ServiceManager
Ed
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•