Pierre Guilluy wrote:Modul8 is a 32bit application because it's built on top of a core macOS framework (Carbon) that weren't ported to 64bit, explaining the 4GB RAM limit.
That being said, the application shouldn't crash under any circumstance.
I guess the problem comes from the dynamic loading/unloading function that's linked to the memory preference you're mentioning, and I'll take a look at that algorithm in order to make sure it works properly.
Ahh okay, I thought Modul8 HD got the 64bit upgrade like Madmapper 2.0 did, that certainly explains that bit of confusion on my part
I've had Modul8 crash very little since I started using it, which is why I was quite surprised when I saw CPU usage hitting numbers I've never seen in years of experimenting with Modul8 and HD clips.
If you need any more logs or anything from me to nail down the loading/unloading function please don't hesitate to ask. Quite happy to provide anything I can to help make things rock solid