Hi all, 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.
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_collector It only traverses objects that return a helper object when QI'ed to nsICycleCollectionParticipant. If it encounters an unknown edge during its traversal, it gives up on that edge; this means that every edge involved in a cycle must be participating, otherwise the cycle will not be found. JavaXPCOM doesn’t handle this, whereas the collector also knows how to walk through the JS heap, and can locate ownership cycles that pass in and out of it. This is for me an important difference. Thanks in advance for any tip. David _______________________________________________ dev-embedding mailing list dev-embedding@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-embedding
