Can someone have a look at this and see if you can tell me why GP crashed when I was closing it down please.
its happened twice since yesterday. Only on exit.
GigPerformer5-2024-09-13-235915.ips.zip (58.9 KB)
Can someone have a look at this and see if you can tell me why GP crashed when I was closing it down please.
its happened twice since yesterday. Only on exit.
GigPerformer5-2024-09-13-235915.ips.zip (58.9 KB)
It’s a crash in the SkyLight framework - that’s a private framework that Apple uses - applications have no direct access to it. That framework handles window management, display management and so forth. I see you’re running 14.6.1 – that’s so new, wouldn’t surprise me if it’s still buggy.
GP isn’t even doing anything — the stacktrace is showing a standard message processing loop that macOS handles and the error suggests memory corruption (freeing an unallocated pointer in the private frameworks - meaning not a GP pointer, for example)
What changed since yesterday?
Thread 0 Crashed:: HotFudge Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x19dbe55f0 __pthread_kill + 8
1 libsystem_pthread.dylib 0x19dc1dc20 pthread_kill + 288
2 libsystem_c.dylib 0x19db2aa30 abort + 180
3 libsystem_malloc.dylib 0x19da3adc4 malloc_vreport + 896
4 libsystem_malloc.dylib 0x19da3e430 malloc_report + 64
5 libsystem_malloc.dylib 0x19da58494 find_zone_and_free + 528
6 SkyLight 0x1a33ec884 displayWillConfigNotifyProc + 724
7 SkyLight 0x1a33e5544 CGSPostLocalNotification + 164
8 SkyLight 0x1a33e5150 (anonymous namespace)::notify_datagram_handler(unsigned int, CGSDatagramType, void*, unsigned long, void*) + 116
9 SkyLight 0x1a3784a5c CGSDatagramReadStream::dispatchMainQueueDatagrams() + 228
10 SkyLight 0x1a3784958 invocation function for block in CGSDatagramReadStream::mainQueueWakeup() + 28
11 libdispatch.dylib 0x19da6b750 _dispatch_call_block_and_release + 32
12 libdispatch.dylib 0x19da6d3e8 _dispatch_client_callout + 20
13 libdispatch.dylib 0x19da7bbb8 _dispatch_main_queue_drain + 988
14 libdispatch.dylib 0x19da7b7cc _dispatch_main_queue_callback_4CF + 44
15 CoreFoundation 0x19dd3ead4 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
16 CoreFoundation 0x19dcfc258 __CFRunLoopRun + 1996
17 CoreFoundation 0x19dcfb434 CFRunLoopRunSpecific + 608
18 HIToolbox 0x1a84a519c RunCurrentEventLoopInMode + 292
19 HIToolbox 0x1a84a4fd8 ReceiveNextEventCommon + 648
20 HIToolbox 0x1a84a4d30 _BlockUntilNextEventMatchingListInModeWithFilter + 76
21 AppKit 0x1a155acc8 _DPSNextEvent + 660
22 AppKit 0x1a1d514d0 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700
23 AppKit 0x1a154dffc -[NSApplication run] + 476
24 GigPerformer5 0x10489ce60 0x104204000 + 6917728
25
Thanks David.
Nothing in GP seems to have been affected.
The only difference yesterday was i took my MacBook out of the house as we had a rehearsal. Could have thrown something off not having the usual peripherals attached maybe? It booted ok when i was there, but when i got home and opened the lid the i saw the crash report. Then it happened again this morning at home with everything plugged in as normal.
Were you running on battery?
Did you just “sleep” the laptop after rehearsal?
Right - I wouldn’t expect that - the issue has nothing really to do with GP itself.
I never turn my laptop off at home, it’s always just sleep mode when not in use. I did turn it off when I took it out but only put it to sleep coming back.
Hmm, yes for most of the night (didn’t mean to, just forgot to plug it in). It got down to 18% when I realised, but it was at 28% when I packed up. It was still charging when I closed the lid though, and was on power at home when it happened again this morning.
It’s not happened since though. ive opened and closed GP a few times just to make sure.
As a general matter, I NEVER use sleep mode – I’ve been bitten too many times by drivers that don’t quite handle things perfectly. I always shut down after use and then restart.
I think we’ve recommended before as a best practice to never use sleep mode.
I always sleep my Mac. Never had an issue so far.
Strangely though, if i leave GP and Logic open, with GP in the foreground, when i bring the Mac out of sleep GP has a corrupt screen \\9all white until i roll the mouse pointer over areas of it) and i normally have to re start it. If its not at the front its fine (and other programs dont behave like this).
Not a big deal, just an observation.
Hmmm, 4th one in 24 hours with nothing new added.
What do you mean by that?
What do you mean by what do I mean?
You wrote that nothing new within 24h
This is just a problem with different “first” languages.
@pianopaul Dave meant that he had a 4th crash within a single day although nothing changed.
My position still is that sleep-mode is not recommended - you should always power down and start up before using GP. While I agree that nothing much happens from a crash at power down, I would be concerned that “something” might not have reset properly when it has to continue from sleep-mode and that’s asking for trouble.
I dont disagree with you about powering down, but in my own experience I haven’t had an issue that I know of when I haven’t.
Saying that, I have had a few in the past when ive put my Mac to sleep while it was saving. This is of course my error and done by mistake. I don’t do that anymore.
I know a reboot sorts most issues out so im not against doing it when errors start appearing.
My concern would be that errors start appearing while you’re in the middle of a show!
I would also travel to the gigs and rehearsals with the Mac turned off. Thats the only time this leaves my desk.
I must admit that I’ve been getting crashes when I exit any Gig file (even an empty one) since a couple of days, too, even though I shut down my Mac every night.
It’s reproducible and only happens with version 4.8.2 and with the laptop closed and connected to an external monitor (via my USB-C hub). It doesn’t crash when the lid is open and also not with 5.0.9.
Like @Dave_bass5 I believe nothing serious has changed on my computer since then either (MacBook Pro M3 with Sonoma 14.6.1).
So it worked fine (for how long) until a couple of days ago? Something clearly changed on your system, there’s no magic.
Also, a search for “ windowserver crash skylight” returns many results.