Apache OpenOffice (AOO) Bugzilla – Issue 47816
23.6% of exporting/Importing 89 DocBook XML files fails if Java 5.01 enabled
Last modified: 2005-06-20 10:00:50 UTC
In the DocBook Load/Save-Test where 89 DocBook XML files (in the past 120) loaded and saved as DocBook XML files 23.6% failing if in the Office is Java 5.01 enabled and not Java 1.4.2_08 (=latest and greatest Java 1.4 version from sun.com). I will attach the *.res-files from the testtool which can be visualized with the testtool application inside OOo.
cc'ing: SUS, MIB Here are the names of the failed ("General Input/Output error.") testdocs with Java 5.01: - Loading sect1.002.xml - Loading section.001.xml - Loading section.002.xml - Loading section.003.xml - Loading segmentedlist.001.xml - Loading segmentedlist.002.xml - Loading table.001.xml - Loading table.002.xml - Loading table.003.xml - Loading table.004.xml - Loading table.005.xml - Loading table.006.xml - Loading template.xml - Loading toc.001.xml - Loading ulink.001.xml - Loading variablelist.001.xml - Loading variablelist.002.xml - Loading variablelist.003.xml - Loading variablelist.004.xml - Loading xref.001.xml - Loading xrefstyle.001.xml
SUS->JSI: Tested two sect1.002.xml and template.xml works for me on WindowsXP with Java 5.0_01 and Java 5.0_00 and SRC680_m93. Please set under tools-options-staroffice-java the Java Environment Variable for debugging, e.g. -DXSLTransformer.statsfile=D:\offices\src680_m93_en-US\xslt_debug.txt
Created attachment 25264 [details] Java 5.01 results
Created attachment 25265 [details] Java 1.4.2_08 results
Important: Please also try to load the exported documents! It seems to be a problem which occours after some time and not in general.
SUS->LO: Note that there are 21 documents have a deprecated doctype, which is not '-//OASIS//DTD DocBook XML V4.1.2//EN' and can only be loaded as text file. A general application error (C++ Pure Virtual Function call) occurs, when using the test tool. Obviously Java VM shuts down, as static variabels will be reinitialized (ie. the randam set XSLT debug output path). If all documents are dropped into the title bar it can not be reproduced. Seems to be a Java problem as it does not work with JDK 1.5.0_00, JDK 1.5.0_01 but runs without error with JDK 1.4.2_08 and JDK 1.5.0_02. Unfortunately we are going to ship with JDK 1.5.0_01 (cp. Release Meeting protocol 21.3).
Created attachment 25337 [details] Testtool log using Java 1.5.0_02
Created attachment 25338 [details] Java class enhancing XSLT debug output
Created attachment 25339 [details] Java class enhancing XSLT debug output
SUS->JSI: Seems the test didn't run till the end, I have to repeat it over week-end. SUS->LO: BTW seems that 'sourcebaseurl' is never provided to the XSLT processor
Generated two crash reports to be found under: stack id 178395
It looks like this was fixed, when the memory leak in the XSLT filter was fixed recently (see issue 48384) please confirm and close if this is the case.
yes and ok. *** This issue has been marked as a duplicate of 48384 ***
verified.
closing