I saw a post regarding a similar issue in 2009, but I believe my situation is a bit different. I'm using HtmlUnit, which has a repackaged Rhino distribution as its javascript engine.
I've observed numerous JVM crashes due to Out Of Memory errors, and the hprofs indicate that there is a large amount of memory taken up by HtmlUnit clients that are referenced by the Finalizer queue ultimately by way of Rhino's NativeGenerator. In some cases these HtmlUnit client instances have been sitting in the Finalizer queue for over an hour, through multiple full GCs. For some reason they appear to be stuck there. I'm going to try to call the finalizer execution manually, but I was wondering why the NativeGenerator needs to have a finalize() method at all, and if the cleanup could be accomplished in any other way through a direct call to clean up its mess. Thanks, Dan _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
