On 06/02/2015 02:32 PM, Lionel Elie Mamane wrote:
So, if you would like to work on that (which would make me happier),
then apply the attached patch, then:
make JunitTest_dbaccess_complex
several times in a row, and you should get the problem. If not, try
uncommenting more "@Test" instances.
Thanks for the reproducer. Looking into it a bit, it smells like a
reincarnation of an ages-old phenomenon where the JVM garbage-collects
objects "too aggressively" (i.e., with the object still nominally on the
call stack, but optimized away) and we thus send a release call from
Java URP to binary URP too soon. I'll look into it further.
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.