JVM crashes on WinXP about java-simple-serial-connector HOT 3 CLOSED

I poked through the crash dump a little bit.  I'm not totally versed in 
interpreting it's contents but I noticed you had over 300 cron4j threads.  Also 
at the bottom it says the heap is at 100% capacity.  I'm wondering if maybe a 
scheduled task is not exiting cleaning so it's threads are piling up?  It may 
just be coincidence that it failed in JSSCs domain.

Hope this helps,
Charles

Sorry, I did not notice that the heap space was at 100%. Thus the 
EXCEPTION_ACCESS_VIOLATION makes sense. I'm going to analyse the issue. Thanks 
a lot for the hint.

Regards,
Nils

Hello Nils, try to check your code in profiler. As I understand you have a 
memory leak in your code. jSSC is strongly tested for memory leakage, and I 
have apps with one year uptime in my automation system.

Best regards, Sokolov Alexey.