search

Espigah / java-simple-serial-connector

Automatically exported from code.google.com/p/java-simple-serial-connector
0 stars 0 forks source link

JVM crashes on WinXP #34

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. The problem is hardly to reproduce because it occurs only after multiple 
hours (4 - 7 hours).

What is the expected output? What do you see instead?
I expect it to work, but I see a dump file (see attachment).

What version of the product are you using? On what operating system?
I'm using version 0.9 with a fix for Mac OS 10.8. The error occurs on WinXP SP 3

Please provide any additional information below.
The JVM crashes in the SerialNativeInterface.waitEvents() methods. We are using 
the event listener to become notified if there is new data available.
On Mac OS it seems to work fine. This meens until now we did not have the bug 
on Mac OS X :)

Any Idea? Or need additional Information?

Original issue reported on code.google.com by nils.ste...@gmail.com on 28 Feb 2013 at 9:52

Attachments:

GoogleCodeExporter commented 9 years ago 
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

Original comment by charles....@gmail.com on 28 Feb 2013 at 11:08

GoogleCodeExporter commented 9 years ago 
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

Original comment by nils.ste...@gmail.com on 28 Feb 2013 at 11:26

GoogleCodeExporter commented 9 years ago 
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.

Original comment by scream3r.org@gmail.com on 3 Mar 2013 at 12:39