Dear Stephan Bergmann,
This bug has been in ASSIGNED status for more than 3 months without any
activity. Resetting it to NEW.
Please assigned it back to yourself if you're still working on this.
Dear Stephan Bergmann,
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
On master towards LO 6.4, the Java baseline is >= 7 now since <https://gerrit.libreoffice.org/plugins/gitiles/core/+/aafc10c9edb61e13ac557c7e43c8d4a31dce4f37%5E!/> "Bump Java baseline to Java 8", so we can go ahead.
Stephan Bergmann committed a patch related to this issue.
It has been pushed to "master":
Related tdf#116767: Call URLClassLoader.close
It will be available in 6.4.0.
The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
Unlike closing the URLClassLoader obtained via ClassLoaderFactory.getURLClassLoader in scripting/java/com/sun/star/script/framework/provider/java/ScriptProviderForJava.java in the commit of comment 4 (which was not listed among the three files reported by Coverity in comment 0), closing the URLClassLoader obtained via ClassLoaderFactory.getURLClassLoader in the three files reported by Coverity in comment 0 is not (easily) doable: In each case, the URLClassLoader is passed on to other classes that hold references to it, so it must only be closed when those other class instances are finalized (and which happens automatically). So resolving as WONTFIX.
(Details about the Coverity reports mentioned in comment 0 are lost to history, btw.)