I think we saw the same "CGColorSpace.c:223: failed assertion `cs->shouldFree'" message in Neo/J 0.8.x. IIRC, this error happens when the underlying OOo code disposes of images in a different order than they were created. I think JVM keeps track of these color space objects in a stack. I will have to think how I can implement delayed disposing of images that OOo disposed out of order.
As for Neo/J not saving a recoverable file, that seems very strange since the "crash reporting" text is generated by the underlying OOo code. So, clearly OOo's crash handler code is being run but the crash handler code is not saving a recoverable file. Have you seen this behavior in OOo X11?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum