can anyone decipher this crash report for me?

Floating Point's icon

Yes boring, I know, but maybe there's a clue in this report. I keep getting intermittent crashes; have no idea what the cause is. Yes it's max 7, 64-bit version on a mac. Yes I know it's old and I should upgrade, but my OS 10.9.5 can't accommodate version 8, so stuck with 7 for now.

Anyway, any suggestions appreciated; I'm using a little audio, centred around sigmund~ (64-bit version), also use a polybuffer for sample playback. Seems to crash only when audio is switched on.
Thanks...

Process: Max [72077]
Path: /Applications/Max 7/Max.app/Contents/MacOS/Max
Identifier: com.cycling74.Max
Version: 7.3.6 [f3836fc] (7.3.6)
Code Type: X86-64 (Native)
Parent Process: launchd [175]
Responsible: Max [72077]
User ID: 501

Date/Time: 2020-07-06 18:31:45.896 +1000
OS Version: Mac OS X 10.9.5 (13F1911)
Report Version: 11
Anonymous UUID: F236BE30-660F-AA33-B6BB-5D30C3B083C2

Sleep/Wake UUID: 3CC944C6-04F5-4C5F-ACB3-633D5139A48B

Crashed Thread: 29

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT

Thread 0:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib     0x0000000115a0da1a mach_msg_trap + 10
1 libsystem_kernel.dylib     0x0000000115a0cd18 mach_msg + 64
2 com.apple.CoreFoundation     0x000000010e6fff15 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation     0x000000010e6ff539 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation     0x000000010e6fee75 CFRunLoopRunSpecific + 309
5 com.apple.HIToolbox     0x00000001191b0a0d RunCurrentEventLoopInMode + 226
6 com.apple.HIToolbox     0x00000001191b07b7 ReceiveNextEventCommon + 479
7 com.apple.HIToolbox     0x00000001191b05bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
8 com.apple.AppKit     0x0000000113f0524e _DPSNextEvent + 1434
9 com.apple.AppKit     0x0000000113f0489b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
10 com.apple.AppKit     0x0000000113ef899c -[NSApplication run] + 553
11 com.cycling74.Max     0x000000010dc49e81 -[MaxCefApplication run] + 49
12 com.cycling74.chromium     0x000000010fa82311 0x10f966000 + 1164049
13 com.cycling74.chromium     0x000000010fa81c1c 0x10f966000 + 1162268
14 com.cycling74.chromium     0x000000010fac04d0 0x10f966000 + 1418448
15 com.cycling74.chromium     0x000000010fad957a 0x10f966000 + 1521018
16 com.cycling74.chromium     0x000000010fabfe6d 0x10f966000 + 1416813
17 com.cycling74.chromium     0x000000010f9d84b2 0x10f966000 + 468146
18 com.cycling74.Max     0x000000010dd93c50 juce::MessageManager::runDispatchLoop() + 80
19 com.cycling74.Max     0x000000010dc62d87 juce::JUCEApplication::main(juce::StringArray const&) + 59
20 com.cycling74.Max     0x000000010dc62e9e juce::JUCEApplication::main(int, char const**) + 68
21 com.cycling74.Max     0x000000010d904114 start + 52

pdelges's icon

It's the thread 29 that crashed Max, but you sent only the trace for thread 0.

Floating Point's icon

whoops! thanks Patrick at least for taking the time for pointing that out to me.
Here's the correct thread--
Thread 29 Crashed:
0 com.cycling74.Max     0x000000010dcb32e1 juce::InternalTimerThread::getTimeUntilFirstTimer(int) const + 33
1 com.cycling74.Max     0x000000010dcb3034 juce::InternalTimerThread::run() + 110
2 com.cycling74.Max     0x000000010dda4cf9 juce::Thread::threadEntryPoint() + 113
3 com.cycling74.Max     0x000000010dd89360 juce::threadEntryProc(void*) + 56
4 libsystem_pthread.dylib     0x0000000115b22899 _pthread_body + 138
5 libsystem_pthread.dylib     0x0000000115b2272a _pthread_start + 137
6 libsystem_pthread.dylib     0x0000000115b26fc9 thread_start + 13