Multiple Corrupt Patches and GUI freezes

Devbugs/issues
Duffield's icon

Duffield

Hey All,

I'm in a time crunch (as always) and my Max just hasn't been performing properly the past couple months and I have an increase in seemingly corrupt patches and objects (or simple objects aren't behaving the way they should be).

A month ago I had an issue where for a client an object simply stopped working. After 3 hours I assumed that perhaps the patch was somehow corrupt and I had to surgically delete entire blocks of code until I found the issue.

Last night, my patch is working fine. Nothing changes, load it up today and the line object isn't going to its destination. In fact, no line objects work properly. Attached is my current patch with this issue. Is it the same on anyone else's computer? ,I'm trying to determine whether it's the patch, Max, or my computer. Additionally, patch cables are simply freezing and not "connecting" to objects but to random parts in the background.

I have tried:

  1. Turning on and off the Computer ;)

  2. Deleting, reinstalling Max deleting Cycling74 preferences

  3. Saving As, and Copy Compressed and making a new patch.

Any other things to test / try?

Max Version:
7.3.5 running in 32-bit mode.

My Computer:
OSX Sierra 10.12.6
MacBookPro11,5
Intel Core i7
Processor Speed: 2.5 GHz
RAM: 16GB
AMD Radeon R9 M370X 2048 MB

Thanks in advance!

forum-test.maxpat
Max Patch


Roland Cahen's icon

Roland Cahen

I recently encountered several times issues of the same kind on Max9 MacOS Tahoe and previous OSs. Sometimes line objects work normally, sometimes nothing comes out of them. How odd and annoying !

TFL's icon

TFL

I see four possible causes for this

  • you stopped the scheduler by mistake by pressing cmd + . (You can resume it with cmd + r )

  • You have a max patch or a third party external in your Max search path called "line". You can search for it in the Max Files Browser

  • The issues comes from your patch, maybe sometimes the wrong message (or no message at all) are sent to [line], but hard to tell if you don't provide a patch

  • It's a genuine bug, in which case it might be worth reporting it by submitting a support ticket with an example patch.