EventThread crashing with 1.7.0_12-ea-b08
Scott Palmer
swpalmer at gmail.com
Sun Feb 3 08:42:12 PST 2013
I have seen similar crashes on the event thread (reported to Oracle's bug database just yesterday).
Here's the relevant part of mine from 1.7.0_13:
Crashed Thread: 21 Java: AWT-EventQueue-0
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008
VM Regions Near 0x8:
-->
__TEXT 00000001037a4000-00000001037b5000 [ 68K] r-x/rwx SM=COW /Library/Java/JavaVirtualMachines/jdk1.7.0_13.jdk/Contents/Home/bin/java
Application Specific Information:
*** error for object 0x7fa5be280a08: pointer being freed was not allocated
Thread 21 Crashed:: Java: AWT-EventQueue-0
0 libsystem_kernel.dylib 0x00007fff903e6212 __pthread_kill + 10
1 libsystem_c.dylib 0x00007fff913d2af4 pthread_kill + 90
2 libsystem_c.dylib 0x00007fff91416dce abort + 143
3 libsystem_c.dylib 0x00007fff913ea959 free + 392
4 libdcpr.dylib 0x00000001599b3183 dcPool_endCycle + 219
5 libdcpr.dylib 0x00000001599b431b dcPathStore_reset + 136
6 libdcpr.dylib 0x00000001599bade5 reset + 52
7 libdcpr.dylib 0x00000001599b4bf5 Java_sun_dc_pr_PathFiller_reset + 59
8 ??? 0x00000001049f2a26 0 + 4372507174
9 ??? 0x0000000104a01b6c 0 + 4372568940
Regards,
Scott
On 2013-02-03, at 11:20 AM, Paul Taylor <paul_t100 at fastmail.fm> wrote:
> Using the latest early access version of Java
>
> macbook:jaikoz paul$ java -version
> java version "1.7.0_12-ea"
> Java(TM) SE Runtime Environment (build 1.7.0_12-ea-b08)
> Java HotSpot(TM) 64-Bit Server VM (build 24.0-b28, mixed mode)
>
>
> My application crashed on the Event Thread:
>
> ................................
>
> ...............................
> Thread 24 Crashed:: Java: AWT-EventQueue-0
> 0 libsystem_kernel.dylib 0x00007fff9208a212 __pthread_kill + 10
> 1 libsystem_c.dylib 0x00007fff937cfaf4 pthread_kill + 90
> 2 libsystem_c.dylib 0x00007fff93813dce abort + 143
> 3 libjvm.dylib 0x0000000103f8ddfd os::abort(bool) + 25
> 4 libjvm.dylib 0x0000000104092506 VMError::report_and_die() + 2316
> 5 libjvm.dylib 0x0000000103f8f68f JVM_handle_bsd_signal + 1073
> 6 libsystem_c.dylib 0x00007fff937bc8ea _sigtramp + 26
> 7 libsystem_c.dylib 0x00007fff937e9e66 szone_free + 1922
> 8 com.apple.CoreFoundation 0x00007fff8f40ddd3 CFRelease + 1571
> 9 com.apple.CoreFoundation 0x00007fff8f439434 __CFBasicHashReplaceValue + 180
> 10 com.apple.CoreFoundation 0x00007fff8f411fbd CFDictionarySetValue + 189
> 11 libosxui.dylib 0x000000015e198728 Java_apple_laf_JRSUIControl_paintChangesImage + 154
> 12 ??? 0x0000000104897cd8 0 + 4371086552
> 13 ??? 0x000000010488b1d4 0 + 4371034580
> 14 ??? 0x0000000104a14d70 0 + 4372647280
>
> ......................
> ......................
>
> Thread 24 crashed with X86 Thread State (64-bit):
> rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x000000016251daf8 rdx: 0x0000000000000000
> rdi: 0x000000000000c603 rsi: 0x0000000000000006 rbp: 0x000000016251db20 rsp: 0x000000016251daf8
> r8: 0x00007fff7b92e278 r9: 0x000000016251dad0 r10: 0x0000000020000000 r11: 0x0000000000000206
> r12: 0x0000000104378f60 r13: 0x00000001039b1000 r14: 0x0000000162520000 r15: 0x0000000103f916de
> rip: 0x00007fff9208a212 rfl: 0x0000000000000206 cr2: 0x00007fff7b927fe8
> Logical CPU: 0
>
> I have the full output but have just posted the pertitent part here, is this a known bug, can anybody parse this ?
>
> The crash conditons cannot be reproduced, it seems to crash at random
>
More information about the macosx-port-dev
mailing list