Hi,
As the java's stack management still is the problem for LibreOffice on
Linux [1], I had an idea (disclaimer: I use Windows for development, and
I have no Java experience, so I don't volunteer for the hardest part):
Currently we have a test for working OpenCL implementation, that
launches on certain conditions to disable its use if test is failed.
Cannot we do the same for Java? E.g., spawn a separate process, that
would do something simple with Java, which is known to segfault on the
problem, and on failure, disable using the selected JVM (and show a
warning)? And launch the test at first run (on user's profile creation);
on JVM selection in advanced options; after a crash (in recovery).
Does that make sense? I suppose it could avoid having blacklists of
Java+kernel combinations etc, and be good for end users that suffer from
the crashes: they would both not avoid crashes, and be informed.
[1] https://bugs.documentfoundation.org/show_bug.cgi?id=108619
--
Best regards,
Mike Kaganski
Context
- 32bitjavacrash workaround? · Kaganski Mike
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.