Hi Archie,
Archie Cobbs wrote:
We got a core dump from the JDK running Batik. The same problem was previously reported on this list:
http://koala.ilog.fr/batik/mlists/batik-users/archives/msg05946.html
Although this is obviously a JVM bug and not a Batik bug, the last comment to this posting..
http://forum.java.sun.com/thread.jspa?threadID=560000&messageID=2752247
I don't know Ernimril is but from everything I know he is wrong in this case. It is true that Swing is off limits out of the AWT thread and drawing to Component.getGraphics (or caching the Graphics passed to paint) would be problematic.
However my understanding is that, Java2D _should_ work fine in any single thread - all our drawing is restricted to either the Update thread or the GVT render thread (never both).
seems to imply that the bug is being *triggered* by Batik's incorrectly invoking AWT methods not from within the Swing thread. Indeed, from the stack trace it appears Batik is invoking sun.java2d.SunGraphics2D.draw() from a different thread than the AWT thread.
Is this analysis correct? Or is the stack trace legitimate?
The stack trace looks fine, but I've always understood that rendering to an offscreen buffer was fine as long as the drawing is done in one thread.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
