While working on a large patch, the following sequence crashes Max pretty reliably: close patch, re-open, crash. The crash is always in getbytes(), with a log as follows
Thread 0 Crashed:
0 com.cycling74.MaxMSP46 0x00067c8f memoryheap_getbytes(_memoryheap*, short) + 171 (utilities.c:260)
1 com.cycling74.MaxMSP46 0x00067e2c getbytes + 42 (utilities.c:232)
2 com.cycling74.MaxAPI 0x01809b02 getbytes + 38
3 com.cycling74.zl 0x16e95e8d zl_new + 126
I don't actually believe that zl is buggy, but suspect that some object is incorrectly deallocating memory when I close my patch.
The culprit could be anywhere in 500MB in subpatches using about 200 externals. Even a binary search is going to be pretty tedious. Does anyone have suggestions for tracking down getbytes/freebytes misbehavior more efficiently. I have the Apple developer tools installed.
I'd be happy to send a complete crash log, but if I'm right and the real problem is occurring microseconds before the crash, then it's probably moot.
Thanks for any ideas,