Register
c[ode]clap»Forums»Version 0.9.0 And 0.9.1 Crash On macOS Catalina
Yuval Dolev
7 posts
Version 0.9.0 And 0.9.1 Crash On macOS Catalina
2 weeks ago Edited by Yuval Dolev on Nov. 21, 2019, 1:18 a.m.
Hello,

I tried to use both 0.9.0 and 0.9.1 versions of codeclap on my MacBook Pro 13 inch with touch bar, but it crashes a few seconds after it starts up.

When I start codeclap up, it opens for a second and then crashes with the following error:
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
Process:               codeclap.osx [54812]
Path:                  /Applications/codeclap.app/Contents/MacOS/codeclap.osx
Identifier:            cc.codeclap.app
Version:               0.9.1 (0.9.1)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           codeclap.osx [54812]

Date/Time:             2019-11-21 03:15:33.822 +0200
OS Version:            Mac OS X 10.15
Report Version:        12
Bridge OS Version:     3.0 (14Y905)

Time Awake Since Boot: 180000 seconds

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    LIBSYSTEM, [0x2]

Application Specific Information:
objc_msgSend() selector name: options
assertion failure: "((void *)0) == tsd->NSCurrentOpenGLContext" -> %lld


Thanks,
Yuval Dolev
spx
119 posts / 1 project
Version 0.9.0 And 0.9.1 Crash On macOS Catalina
2 weeks ago
Hi,

it seems there were similar reports for other OpenGL applications during 10.15 Betas but apparently those were fixed by Apple at some point, unfortunately at the moment for Catalina I only have 10.15.1 to test with. Since there is no additional information in "OS Version", what update state is this?

Is there any kind of stacktrace for any of the threads included in the report? Do you see any content drawn in the window at any point?

Thanks
Yuval Dolev
7 posts
Version 0.9.0 And 0.9.1 Crash On macOS Catalina
2 weeks ago Edited by Yuval Dolev on Nov. 21, 2019, noon
Hi,
I'm using macOS Catalina Beta 8 (19A558d).

Here is the stacktrace for all the threads. The main thread is the thread that crashes.
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff6d0aef76 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff6d0af4dc mach_msg + 60
2   com.apple.SkyLight            	0x00007fff63cc04d7 __add_structural_region_block_invoke + 210
3   com.apple.SkyLight            	0x00007fff63d30e1e SLSRegionPerformWithSerializedBytes + 82
4   com.apple.SkyLight            	0x00007fff63cc03d4 add_structural_region + 739
5   com.apple.SkyLight            	0x00007fff63c6a43e add_structural_region_of_type + 69
6   com.apple.AppKit              	0x00007fff32cd3e33 _NXSetTrackingRect + 532
7   com.apple.AppKit              	0x00007fff32cd3bea _NSSetTrackingRect + 482
8   com.apple.AppKit              	0x00007fff32cd37d4 _setTrackingRect + 270
9   com.apple.AppKit              	0x00007fff32cd3630 -[NSWindow(NSTrackingAreas) _setTrackingRect:inside:owner:userData:useTrackingNum:install:] + 426
10  com.apple.AppKit              	0x00007fff32cd3478 -[NSWindow(NSTrackingAreas) _setTrackingRect:inside:owner:userData:useTrackingNum:] + 47
11  com.apple.AppKit              	0x00007fff32cd31cb -[NSView(NSInternal) _installTrackingArea:] + 423
12  com.apple.AppKit              	0x00007fff32cd1345 -[NSView(NSInternal) _updateTrackingAreasWithInvalidCursorRects:] + 1844
13  com.apple.AppKit              	0x00007fff32cd14a5 -[NSView(NSInternal) _updateTrackingAreasWithInvalidCursorRects:] + 2196
14  com.apple.AppKit              	0x00007fff32cd099f _NSWindowDisplayCycleUpdateStructuralRegions + 319
15  com.apple.AppKit              	0x00007fff32cce47f __NSWindowGetDisplayCycleObserverForUpdateStructuralRegions_block_invoke + 420
16  com.apple.AppKit              	0x00007fff32cbb455 NSDisplayCycleObserverInvoke + 155
17  com.apple.AppKit              	0x00007fff32cbb01c NSDisplayCycleFlush + 977
18  com.apple.QuartzCore          	0x00007fff4159d5ce CA::Transaction::run_commit_handlers(CATransactionPhase) + 100
19  com.apple.QuartzCore          	0x00007fff4159cf20 CA::Transaction::commit() + 224
20  com.apple.AppKit              	0x00007fff3348e320 __62+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayLink]_block_invoke + 266
21  com.apple.AppKit              	0x00007fff3348e748 ___NSRunLoopObserverCreateWithHandler_block_invoke + 41
22  com.apple.CoreFoundation      	0x00007fff359f476e __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
23  com.apple.CoreFoundation      	0x00007fff359f4694 __CFRunLoopDoObservers + 457
24  com.apple.CoreFoundation      	0x00007fff3599780b __CFRunLoopRun + 1219
25  com.apple.CoreFoundation      	0x00007fff359970c3 CFRunLoopRunSpecific + 499
26  com.apple.HIToolbox           	0x00007fff34524f2d RunCurrentEventLoopInMode + 292
27  com.apple.HIToolbox           	0x00007fff34524c6d ReceiveNextEventCommon + 600
28  com.apple.HIToolbox           	0x00007fff345249f7 _BlockUntilNextEventMatchingListInModeWithFilter + 64
29  com.apple.AppKit              	0x00007fff32bceee4 _DPSNextEvent + 990
30  com.apple.AppKit              	0x00007fff32bcdc50 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
31  com.apple.AppKit              	0x00007fff32bc8395 -[NSApplication run] + 658
32  codeclap.osx                  	0x000000010a472d05 main + 533
33  libdyld.dylib                 	0x00007fff6cf662a5 start + 1

Thread 1:
0   libsystem_pthread.dylib       	0x00007fff6d16f5b4 start_wqthread + 0

Thread 2:
0   libsystem_pthread.dylib       	0x00007fff6d16f5b4 start_wqthread + 0

Thread 3:
0   libsystem_pthread.dylib       	0x00007fff6d16f5b4 start_wqthread + 0

Thread 4:
0   libsystem_pthread.dylib       	0x00007fff6d16f5b4 start_wqthread + 0

Thread 5:: CVDisplayLink
0   libsystem_kernel.dylib        	0x00007fff6d0b5f6e __terminate_with_payload + 10
1   libsystem_kernel.dylib        	0x00007fff6d0d04ba abort_with_payload_wrapper_internal + 119
2   libsystem_kernel.dylib        	0x00007fff6d0d04c5 abort_with_payload + 9
3   libsystem_c.dylib             	0x00007fff6d03ca07 _os_crash_fmt.cold.1 + 55
4   libsystem_c.dylib             	0x00007fff6cfcf876 _os_crash_fmt + 154
5   com.apple.AppKit              	0x00007fff32d91994 __NSAppKitFinalizeThreadData + 663
6   libsystem_pthread.dylib       	0x00007fff6d170413 _pthread_tsd_cleanup + 551
7   libsystem_pthread.dylib       	0x00007fff6d17316f _pthread_exit + 70
8   libsystem_pthread.dylib       	0x00007fff6d172d81 _pthread_start + 136
9   libsystem_pthread.dylib       	0x00007fff6d16f5d7 thread_start + 15

Thread 6:: com.apple.NSEventThread
0   libsystem_kernel.dylib        	0x00007fff6d0aef76 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff6d0af4dc mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff3599844b __CFRunLoopServiceMachPort + 322
3   com.apple.CoreFoundation      	0x00007fff359979e7 __CFRunLoopRun + 1695
4   com.apple.CoreFoundation      	0x00007fff359970c3 CFRunLoopRunSpecific + 499
5   com.apple.AppKit              	0x00007fff32bd651a _NSEventThread + 132
6   libsystem_pthread.dylib       	0x00007fff6d172d76 _pthread_start + 125
7   libsystem_pthread.dylib       	0x00007fff6d16f5d7 thread_start + 15


I'm seeing codeclap drawing in the window for a second, and then it crashes with this stack trace.
Yuval Dolev
7 posts
Version 0.9.0 And 0.9.1 Crash On macOS Catalina
2 weeks ago
I updated to beta 10 and now it works.

Thanks for the help!
spx
119 posts / 1 project
Version 0.9.0 And 0.9.1 Crash On macOS Catalina
1 week, 6 days ago Edited by spx on Nov. 21, 2019, 9:11 p.m.
yuvaldolev
I updated to beta 10 and now it works.

Thanks for the help!


Glad this is solved for you. From what I found Apple fixed this in beta 9.
There are distant plans to switch the renderer to Metal at some point to avoid any OpenGL shenanigans apple may come up with. Not that OpenGL isn't deprecated anyway.