On Sep 8, 2014, at 20:08, Sergey Bylokhov wrote:
> The request was reopened and additional information was added.
Found the ticket: https://bugs.openjdk.java.net/browse/JDK-8057830
> Thanks for your report!
Thank you, Sergey.
Very much appreciated.
This bug and the one mentioned in
http://ma
Hi, Hendrik.
The request was reopened and additional information was added.
Thanks for your report!
On 04.09.2014 13:26, Hendrik Schreiber wrote:
On Sep 2, 2014, at 16:56, Hendrik Schreiber wrote:
Hey Anthony,
... or actually anyone else with access to the bug database ...
could you please
On Sep 2, 2014, at 16:56, Hendrik Schreiber wrote:
> Hey Anthony,
... or actually anyone else with access to the bug database ...
> could you please check whether bug report with review id JI-9014446 was also
> closed, because nobody was able to reproduce it?
Any chance you can you check this
Hey Anthony,
could you please check whether bug report with review id JI-9014446 was also
closed, because nobody was able to reproduce it?
If so, the bug also re-appeared in the final Java 8_u20.
It seems to be connected to a message in standard error:
exception in QueueFlusher:
java.lang.Runti
On Aug 21, 2014, at 10:10, Hendrik Schreiber wrote:
> I was wondering what is the best way to submit crash logs of non-repeatable
> VM crashes?
Alright - I simply filed a bunch of bugs.
But I really think it would be beneficial, if there was a way one could
automatically send crashlogs to som
Hey,
I was wondering what is the best way to submit crash logs of non-repeatable VM
crashes?
E.g. I have this crash log containing:
OS Version: Mac OS X 10.9.4 (13E28)
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x
[...]
Thread 24::
