Closed
Bug 86789
Opened 24 years ago
Closed 24 years ago
the bridge does not deallocate objects
Categories
(Core Graveyard :: Java to XPCOM Bridge, defect, P1)
Core Graveyard
Java to XPCOM Bridge
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: blackconnect, Assigned: blackconnect)
References
Details
Attachments
(1 file)
|
19.91 KB,
patch
|
Details | Diff | Splinter Review |
Once object get used by the bridge it will not be deallocated.
|
Assignee | |
Comment 1•24 years ago
|
||
Make 81122 (Memory leaks) bug to be depended on this one
Blocks: 81122
Priority: -- → P1
|
|
Assignee | |
Comment 2•24 years ago
|
||
|
|
Assignee | |
Comment 3•24 years ago
|
||
The fix is adding refcounting to stubs and proxies.
Another problem is that we have to dealocate proxies with 0 refcount server
side. (On java side, GC do the work. On XPCOM side we have to take care about
it)
The fix is checked in. Closing as fixed.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
|
||
Updated•11 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•