Hi Benjamin, First of all, thanks for your valuable answer.
On 1 Jul., 16:33, Benjamin Smedberg <[email protected]> wrote: > On 7/1/09 5:47 AM, David P rez wrote: > > > We ve made a simple XULRunner app, coded in Java. > > We ve observed that it has huge memory leaks. > > Rewriting the same app in Javascript, we observe no leaks. > > That's certainly possible. JavaXPCOM doesn't have an owner and I may > consider removing it in the next release if we can't find an owner. JavaXPCOM, even when leaky, is very useful, so I wouldn't drop it in the next release. > > > So, we suspect there is some problem with JavaXPCOM. Maybe the > > problem is related with the cycle collector. > >https://developer.mozilla.org/En/Interfacing_with_the_XPCOM_cycle_col... > > Is your code creating object cycles. In most cases if you are in control of > the code you can manually avoid object cycles by nulling references when > they are no longer needed. I suspect adding cycle-collection to the > JavaXPCOM interface would be very difficult, because it would require > knowing all the object edges through the Java GC heap. I have made simply an app that loads an URL in a browser, waits through events till the page is loaded, and emulates mouse clicks in certains part of the page. In Java code I need to make XPCOM calls to objects. For reacting to events (page loaded), I need to create Java objects that implements certain nsIXXXX interface. Maybe the cycling collector isn't the real problem, it's just a supposition. I have tried to apply this patch and the memory leaks have improved a lot. https://bugzilla.mozilla.org/show_bug.cgi?id=501930 > --BDS _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
