Comment 3 for bug 227217

> - is this reproducible in intrepid?
This is not even deterministically reproducible on my own machine(s).
It happened only a few times, up to now.

But due to the fact that the error occurs outside the Java VM, I
decided to report it nonetheless.

> - could you provide a test case to reproduce the crash?
As stated above: I'm sorry, I can't (or at least: I didn't manage
until now.) The problem is occurring in a large long-running
application with a memory usage above 100MB.

If I manage to track down the problem (or otherwise am able to
provide more, useful information) I will definitely do so. But
at the moment, I really have no clue about how to get an isolated
deterministic minimal case.

I did however report the error because
* the error occurred more than once
* the application crashing the VM is pure-java, so the code as-is
 cannot directly cause a crash outside the VM due to some programming bug.
* I hope that I will manage to track it down one day or
 that other users submit bug-reports that can be linked to this one.

>This bug report will be marked for expiration in 59 days if no further activity occurs.
I really wonder why difficult bugs are scheduled for removal this soon. It would really
be sad if due to the fact that this bug is going to be expired without being resolved
would force me to abandon open-jdk (just because I cannot afford the downtime due
to unexpected crashes).