the bridge does not deallocate objects

VERIFIED FIXED

Status

P1
normal
VERIFIED FIXED
17 years ago
4 years ago

People

(Reporter: blackconnect, Assigned: blackconnect)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

17 years ago
Once object get used by the bridge it will not be deallocated.
(Assignee)

Comment 1

17 years ago
Make 81122  (Memory leaks) bug to be depended on this one
Blocks: 81122
Priority: -- → P1
(Assignee)

Comment 2

17 years ago
Created attachment 40068 [details] [diff] [review]
fix for the bug
(Assignee)

Comment 3

17 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
Last Resolved: 17 years ago
Resolution: --- → FIXED

Comment 4

16 years ago
-- Very old bug. Marking Verified.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.