On Aug 17, 2006, at 22:34, Jeremias Maerki wrote:
Hi,
Uh, sorry, I somehow missed your hint about "not thread safe". I
thought
it was something simpler. Your additional details seem to confirm that
it's about thread-safety.
Seems like the real clue is this:
3, if I close the open-window quite fast(may before the PDF files are
actually generated), and start all 3 again, it will happen 1 of
10-40 times.
Althougn this is quite seldom, but still is not acceptable for my
situation.
Looking at the code, it seems perfectly possible that, if a rendering
is interrupted, a PDFNumber is instantiated, but setNumber() is never
called for it.
Question remains: does the error arise in the thread following the
interrupted one, or in the interrupted thread itself, as a side-
effect of the renderer trying to output a PDFNumber that has been
instantiated?
PDFNumber does have a private static member storing the decimal
format. Maybe this is the bugger here?
Cheers,
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
