You would probably need someone with a debug build of LibO master
branch who can find some way to analyse the Java stack using gdb or
valgrind or some other reporting tool. From what I gather from past
discussions, it is currently actually quite difficult to do that, but
I could be wrong and things could have moved forward since then.
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.