I've been getting a crash recently involving a patch with a number of models and views (wrapped together as modules, in the old Jamoma style). The models are a bit complex, so I tried to trace the problem by deleting sections, reopening the patch and seeing if it still crashed. I think I've traced it to a couple of parameters in the model that are inside of a subpatcher, as well as the corresponding remotes in the view that are also nested in a subpatcher.
I tried simplifying _start.maxpat to make debugging easier, e.g. by deleting duplicates of the module as well as all other objects. I noticed a couple of things in this process:
With the current version of _start.maxpat, Max crashes as soon as the patch is opened. When I tried a version of _start.maxpat containing fewer instances of the model, the crash would only happen when I closed the patch.
With the current version of _start.maxpat, macOS tends to produce an error report consistently, whereas with the simplified version, clicking "Report..." wouldn't bring anything up.
With the simplified version, sometimes opening and closing the patcher several times would lead to the crash.
I've been getting a crash recently involving a patch with a number of models and views (wrapped together as modules, in the old Jamoma style). The models are a bit complex, so I tried to trace the problem by deleting sections, reopening the patch and seeing if it still crashed. I think I've traced it to a couple of parameters in the model that are inside of a subpatcher, as well as the corresponding remotes in the view that are also nested in a subpatcher.
Here's the crash report:
https://gist.github.com/evanmtp/6f58b243404ee3f350732a1d78ca71de
And here are the test files:
test.zip
Steps to reproduce:
I tried simplifying _start.maxpat to make debugging easier, e.g. by deleting duplicates of the module as well as all other objects. I noticed a couple of things in this process: