Forums > MaxMSP

how do i track down what becomes a free object that crashes maxmsp?

September 11, 2013 | 5:38 am

hey there and hello from newb

i get crashes quite consistently with the crahed thread reporting this at the last line….

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.cycling74.Max 0x000369a8 freeobject + 52
1 com.cycling74.Max 0x00036b4f freeobject + 475

its the same two free objects and hex name so i’m thinking that these are the consistent issue in these crashes, no matter whaich thread crashes – the same two are at the last line….

what are free objects? ( i think from reading up a bit – that theyre objects no longer needed and ‘disposed of’ but not too sure…..and how might i track down an object is becoming free and crashing max?


September 11, 2013 | 5:45 am

did you write your own external or use an external library ? a freeobject is usually a fonction inside one max object which is called when the object is destroyed (ie when it is erased form a patcher (not sure, maybe ? or when all the instances of tha tobject are destoryed from the patcher ?) and when a patcher containing said object is closed). Seems related to that. You would have more help maybe in the dev section of the forum.


September 11, 2013 | 5:52 am

yes i have a few 3rd party items loaded – but not necessarily at the time of crashing – although its hard to be sure.

i’ll remove these and retry –

thanks for the input so quickly

CD


Viewing 3 posts - 1 through 3 (of 3 total)