On 14/02/2014 11:41, Michael Hall wrote:
I was under the impressions that however bad my code was it shouldn't cause
Java to crash in this way, is that not correct ?
I believe that is the theory. So you probably did hit on at least an edge case
which the jdk didn't handle as well as you'd hope - if not a actual jdk bug.
But interesting that you think there is a bug in my code that could be causing
this to happen, its only been reported once by one user so going to be
difficult to track down
Probably in or calling into native.
I don't think I said anything about it being your code. Although I would say
it's possible it's your code. I usually tend to suspect mine first in these
situations. Probably doing something strange to hit a jdk edge case.
To be clear I'm not taking any offense that it could be my code, I just
didn't think I could cause a crash. For example in this case if I'm
recursively calling something I would just expect a java
|StackOverflowError, I think if I did hit ||edge case which the jdk
didn't handle as well as hoped that would be a jdk bug in my book. |
||
|My application doesnt really contain any native code written by me, there is a
little bit of Applescript and that is it.|
||
|
Paul|
