Surprise crash

[richmond62]

Suddenly, for no obvious reason after 6 hours solid work . . .

[tperry2x]

From reading that, sounds like a memory allocation issue (malloc).
Plenty or carbon libraries in there, which I thought were supposed to be depreciated now.

With the release of macOS 10.15 Catalina, the Carbon API was officially discontinued and removed

(link)

As I mentioned, many times before, I wouldn't expect the LCC9.6.3 engine to stay running on anything above MacOS 11 as it's not officially supported. What with MacOS also being such a moving target, there could be anything changed by Apple at any time which breaks the engine or makes it unstable.

[richmond62]

Hmm:
-

maalox.jpg (12.9 KiB) Viewed 977 times

-
Good thing I'm only slightly deaf.

[OpenXTalkPaul]

From reading that, sounds like a memory allocation issue (malloc).
Plenty or carbon libraries in there, which I thought were supposed to be depreciated now.

With the release of macOS 10.15 Catalina, the Carbon API was officially discontinued and removed

(link)

Oh my, there does look like there is calls to Carbon stuff, and they're related to NSMenu which seems to be at the root of our newer macOS problems:

56 AppKit 0x7ff808699c6a -[NSApplication(NSResponder) sendAction:to:from:] + 288
57 AppKit 0x7ff80878e7d0 -[NSMenuItem _corePerformAction] + 413
58 AppKit 0x7ff80878e4f2 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 95
59 AppKit 0x7ff8087d8e4f -[NSMenu performActionForItemAtIndex:] + 113
60 AppKit 0x7ff8087d8dd5 -[NSMenu _internalPerformActionForItemAtIndex:] + 82
61 AppKit 0x7ff8087d8c1c -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 101
62 AppKit 0x7ff808772dae NSSLMMenuEventHandler + 1074
63 HIToolbox 0x7ff80e6e334d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1365
64 HIToolbox 0x7ff80e6e279c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 333
65 HIToolbox 0x7ff80e6f73a9 SendEventToEventTarget + 39
66 HIToolbox 0x7ff80e7552e5 SendHICommandEvent(unsigned int, HICommand const*, unsigned int, unsigned int, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 361
67 HIToolbox 0x7ff80e77a457 SendMenuCommandWithContextAndModifiers + 46
68 HIToolbox 0x7ff80e77a405 SendMenuItemSelectedEvent + 344
69 HIToolbox 0x7ff80e77a250 FinishMenuSelection(SelectionData*, MenuResult*, MenuResult*) + 96
70 HIToolbox 0x7ff80e77ac48 MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 625
71 HIToolbox 0x7ff80e77a93e _HandleMenuSelection2 + 456
72 AppKit 0x7ff8086342b9 _NSHandleCarbonMenuEvent + 215
73 AppKit 0x7ff808634126 _DPSEventHandledByCarbon + 54
74 AppKit 0x7ff80849491c -[NSApplication(NSEvent)

On second thought, rather than coming from our xTalk macOS engine, these might be internal 'private symbols' that are names used in AppKit for which Apple never changed the names for (for backwards compatibility)? I see some other recent reports from other projects (WxWidgets) referencing these same pointers crash reporting.

[neville]

If I leave the ide running for days I eventually see a crash - on Ventura. Haven’t had time to try to track it down but I suspect a memory leak in the ide rather than anything wrong with my code which is always immaculate. (Actually the reason I haven’t had time is I am too busy tracking down my own bugs)

I would definitely recommend running a plug-in like Rinaldi to periodically auto save, so you only lose 10 minutes work rather than hours.

[richmond62]

It is extremely easy to run up one's own autosave thing.