On Nov 27, 2007, at 20:06, Andreas L Delmelle wrote:
Hi Chris (and other interested parties)
On Nov 27, 2007, at 18:32, Chris Bowditch wrote:
Andreas L Delmelle wrote:
Cannot reproduce it here...
Strange. The patch is definitely applied and I tried building it
twice just to make sure. The second time it run and generated
about 100 docs before failure.
java.lang.NullPointerException
at
org.apache.fop.fo.properties.PropertyCache.cleanSegment
(PropertyCache.java:99)
... and this line can normally not cause an NPE.
Which JVM did you test it on? Do you run multiple concurrent
threads, or is it just a plain single-threaded iteration?
Sun 1.5.0_12 on Windows XP SP 2.
I tested on Apple JVM 1.4.2 and 1.5.0 on OS X 10.4. Both single-
and multi-threaded.
Heap remains stable here over hundreds of runs.
With multiple concurrent runs, my CPU usage easily reaches 180-190%
(2 CPUs)
Just to confirm:
In the meantime, I have also run some tests with the same document on
Windows XP SP 2 with different versions of the Sun JVM, running 2
concurrent threads on a Centrino Dual Core.
Classes compiled with 1.4 compatibility.
I managed to reproduce the NPE on Java 1.4.2 and 1.5.0, at random
intervals, always between 50 and 250 runs.
The version I just committed (http://svn.apache.org/viewvc?
rev=600195&view=rev) resolves this problem by adding extra null
checks, and should now work on your end as well.
Java 1.6.0 on Windows XP did not seem to have a problem with the
PropertyCache, with or without the extra checks.
OTOH, it does crash eventually, due to a
ConcurrentModificationException thrown at ContextImageCache.getImage
(ImageFactory.java:409)... :/
Cheers
Andreas
