To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=57753 Issue #:|57753 Summary:|Fix JNI-UNO bridge so that the JVM doesn't run out of |memory when a destructor locks the SolarMutex Component:|udk Version:|OOo 2.0 Platform:|All URL:| OS/Version:|All Status:|UNCONFIRMED Status whiteboard:| Keywords:| Resolution:| Issue type:|PATCH Priority:|P2 Subcomponent:|code Assigned to:|sb Reported by:|mtg
------- Additional comments from [EMAIL PROTECTED] Fri Nov 11 08:23:34 -0800 2005 ------- Hi there, As discussed on the udk-dev list, there is a bug in the JNI-UNO bridge, as the JVM's finalizer thread can block if a destructor wishes to acquire the SolarMutex while another thread has already locked it. This results in the JVM garbage collection being stalled, and as a result, it will throw a java.lang.OutOfMemoryError. The attached patch creates a FinalizerThreadPool singleton which holds a queue of objects to be released. The JVM finalizer thread then just adds an object to the queue and returns immediately. The FinalizerThreadPool will then share out the objects to be released to it's various child threads. I will create a reduced test case to demonstrate the error in action. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
