Martin Gallwey wrote:
Hi there,
I wrote some import/export filters and wish to compare the results of a
round tripped document with the original document. Thus, I modified the
DocumentConverter java sample from the SDK and let it loose on my data.
However! On average, the whole JVM crashes on 1 document in 20. This is
bad, as I can't be sure if my filters would result in a crash when in
use in the wild - although I have never experienced a crash when running
in non-batch mode.
Is there any reason why performing a batch conversion using the JNI UNO
bridge to access Java filters for both import and export could cause
problems?
Does anyone have any hints or tips on how to track down this error? Any
obscure logging options in the JNI UNO bridge I can turn on?
The JVM installs a signal handler, so whenever soffice crashes after the
JVM has been started in process (and whether or not that crash is in any
way releated to using Java), you will see some error output from the
JVM. However, this output usually does not help to track down the
problem (as usually the crash is in some part of soffice unrelated to
Java). The best might be to run soffice from within a debugger to get
some more meaningful stacktrace.
-Stephan
Samples of JVM crash logs are attached.
Thanks,
Martin
[...]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
