Hi Hendrik,
JI-9014527 was closed as Incomplete "Not enough information.",
supposedly because there's not a reproducible test case and instructions
to reproduce the issue.
If you come up with a simple test that crashes easily, we can re-open
that bug.
BTW, from the full stack trace in the bug report I can see you're
running some accessibility software on your system because the crash
happens during an a11y callback. This may be a contributing factor to
the crash. You will need to test with and without a11y on, and also
perhaps try another assistive technology (e.g. the built-in VoiceOver
vs. a third-party software) to see if this changes anything.
--
best regards,
Anthony
On 8/28/2014 5:59 PM, Hendrik Schreiber wrote:
Hey guys,
in the current release, i.e.
java version "1.8.0_20"
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode)
there is a bug that causes crashes, because some code calls
Java_sun_lwawt_macosx_LWCToolkit_stopAWTRunLoop with NULL as mediatorObject
(i.e. argument).
I have filed this bug already on 8/25/2014 for 1.8.0_20-ea at
http://bugreport.java.com. There it received review id JI-9014527 and was not
seen ever since.
The crash has re-appeared in the final 1.8.0_20 (the version above). A full
crash log can be found at http://www.beatunes.com/download/stopAWTRunLoop.crash
The most important part is:
Application Specific Information:
*** CFRelease() called with NULL ***
Thread 30 Crashed:: Java: AWT-EventQueue-0
0 com.apple.CoreFoundation 0x00007fff863404c4 CFRelease + 724
1 libawt_lwawt.dylib 0x00000001256fe6b6
Java_sun_lwawt_macosx_LWCToolkit_stopAWTRunLoop + 72
2 ??? 0x000000010fe14714 0 + 4561389332
3 ??? 0x000000010fe0698d 0 + 4561332621
4 ??? 0x000000010fe069d2 0 + 4561332690
5 ??? 0x000000010fe0698d 0 + 4561332621
6 ??? 0x0000000111f3f204 0 + 4596167172
7 ??? 0xf4bbddf7f8000b3f 0 +
17634932822986722111
Could someone with access to the bug system please attach the provided crash
log to the original bug?
And also add the additional info, that this time it happened with the final
1.8.0_20 release?
I have
Thank you - your help is much appreciated.
-hendrik
