mir/libreoffice
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update documentation

Browse Source 
Change-Id: Icd966a850b7c5e276e8b1d74566a4ea02e5b4a5c
This commit is contained in:
Stephan Bergmann
2014-12-11 13:27:26 +01:00
parent ebd2d28c64
commit b09964e97f
1 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
jurt/com/sun/star/lib/util/AsynchronousFinalizer.java
View File

@@ -24,15 +24,17 @@ import java.util.LinkedList;
* Helper class to asynchronously execute finalize methods. * Helper class to asynchronously execute finalize methods.
* *
* <p>Current JVMs seem not to be robust against long-running finalize methods, * <p>Current JVMs seem not to be robust against long-running finalize methods,
* in that such long-running finalize methods may lead to OutOfMemoryErrors. This * in that such long-running finalize methods may lead to OutOfMemoryErrors.
* class mitigates the problem by asynchronously shifting the bodies of * This class mitigates the problem by asynchronously shifting the bodies of
* potentially long-running finalize methods into an extra thread. Classes that * potentially long-running finalize methods into an extra thread. Classes that
* make use of this in their finalize methods are the proxies used in the * make use of this in their finalize methods are the proxies used in the
* intra-process JNI UNO bridge and the inter-process Java URP UNO bridge (where * intra-process JNI UNO bridge and the inter-process Java URP UNO bridge (where
* in both cases finalizers lead to synchronous UNO release calls).</p> * in both cases finalizers lead to synchronous UNO release calls).</p>
* *
* <p>If JVMs are getting more mature and should no longer have problems with * <p>Irrespective whether JVMs are getting more mature and should no longer
* long-running finalize methods, this class could be removed again.</p> * have problems with long-running finalize methods, at least the JNI UNO bridge
* needs some way to stop finalization of proxies (to C++ objects) well before
* process exit, as provided by drain().</p>
*/ */
public final class AsynchronousFinalizer { public final class AsynchronousFinalizer {
public AsynchronousFinalizer() { public AsynchronousFinalizer() {