Fabio De Sanctis De Benedictis

Max 8.3.1 crashes on saving new patches, even if I create one and save before puttong any object inside it.

However it opens and saves old patches. Following the crash report.

I have verified and tested RAM anc HD, they seem ok. I have maintened the system, restarted, but the problem persists. I am on OsX El Capitan 10.11.6 and MacBook Pro mid 2012.

Anonymous UUID: EFFCE981-FDAD-16D1-BF8A-A5D2DBC575E1

Crashed Thread: 0 CrBrowserMain Dispatch queue: 

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)

Exception Codes: 0x0000000000000001, 0x0000000000000000

Crashing on exception: +[NSTextField labelWithString:]: unrecognized selector sent to class 0x7fff75c0cc28

Max 8.3.1 crashes on saving new patches, even if I create one and save before puttong any object inside it.
However it opens and saves old patches. Following the crash report.
I have verified and tested RAM anc HD, they seem ok. I have maintened the system, restarted, but the problem persists. I am on OsX El Capitan 10.11.6 and  MacBook Pro mid 2012.

Crash report (beginning):

Process:               Max [481]
Path:                  /Applications/Max.app/Contents/MacOS/Max
Identifier:            com.cycling74.Max
Version:               8.3.1 [f487da5cc84] (8.3.1)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Max [481]
User ID:               502

Date/Time:             2022-06-22 20:33:03.488 +0200
OS Version:            Mac OS X 10.11.6 (15G22010)
Report Version:        11
Anonymous UUID:        EFFCE981-FDAD-16D1-BF8A-A5D2DBC575E1

Crashed Thread:        0  CrBrowserMain  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
Crashing on exception: +[NSTextField labelWithString:]: unrecognized selector sent to class 0x7fff75c0cc28

Hi,
Max 8.3.1 crashes on saving new patches, even if I create one and save before puttong any object inside it.
However it opens and saves o

max-8-3-1-crashes-on-saving-new-patches

Little update: until 8.2.2 version the problem is not present. From 8.3.0 forward it is present.

I have uninstalled and trashed Application Support cycling74 folder in my account, recreating it, but it is not a valid solution. I can not realize what can be the solution.

Little update: until 8.2.2 version the problem is not present. From 8.3.0 forward it is present.
I have uninstalled and trashed Application Support cycling74 folder in my account, recreating it, but it is not a valid solution. I can not realize what can be the solution.

it was introduced on OSX in 2016 (10.12), and you’re still using 10.11 (2015), hence a crash. Is this happening anytime you try to show a save panel? (Like if you Save As… an existing patch)?

(in any event upgrading the OS would fix it, but I gather that’s not workable for one reason or another… nice job keeping a 2012 machine up and going!)

+[NSTextField labelWithString:]:

This convenience api looks like
it was introduced on OSX in 2016 (10.12), and you’re still using 10.11 (2015), hence a crash.  Is this  happening anytime you try to show a save panel? (Like if you Save As… an existing patch)?

Thank you for reply. The crash happens even if I choose "Save as" in saving a new patch. I supposed it could be connected to API features. But the strange thing is that nothing happens on old patches or using until 8.3.2 Max version. Anyione has any idea about resolving?

P.S.: yes, if possible I would like not upgrading OsX...

HI Fabio, pleased to see you on the Forum. Did you try to trash max preferences as well as every c74 folders (application support, every other c74 folder, depending on you file path) the app itself and then reinstall ?

don't bother cleaning max folders and similar.

Resaving any existing file in same location will

work as expected, also save as template or save as project

works without problems, because filetype is known.

any save dialog with filetype option will crash,

writewave message to buffer~ again works ...

max 8.1.11 works well on macbook 2008 el capitan

don't bother cleaning max folders and similar.
The problem really is Save As... dialog.
Resaving any existing file in same location will
work as expected, also save as template or save as project
works without problems, because filetype is known.
any save dialog with filetype option will crash,
like write buffer~ 
or building collective or standalone

writewave message to buffer~  again works ...
P.S.
max 8.1.11 works well on macbook 2008 el capitan


Yes, I have trashed every Max folder in Preferences and Application support, and reinstalled, if I remember good, without success. Now I try again, if I can in a more radical manner. Today I was in my Institute, on High Sierra Max 8.3.1 runs, so I could try to update, even if I would miss the possibility to use PWGL (the main reason for which I have still El Capitan). Or I will downfrade to 8.2. Meanwhile thanks to everyone for suggestions and help, I will keep you updated on this matter.

Well, until now nothing to be done, I have erased all max folders, restarted the computer, reinstalled, reactivated and restarted, without any success. I suppose it can be a writing problem: if I copy an existing patch in another location, by system operations, max opens and save it, but crashes if I try to save as, or if I try to save a new one. For the moment I must surrender...

I'm afraid that Source Audio is right. I don't have enough experience about API and similar things. Consider that, if you want to continue using PWGL, you might consider dual booting. It depends what are your main targets: Pwgl or the new features of Max 8.3.1. I personally prefer the Bach package, but i know that switching platforms is quite annoying.

mmhh,
I'm afraid that Source Audio is right.  I don't have enough experience about API and similar things. Consider that, if you want to continue using PWGL, you might consider dual booting. It depends what are your main targets:  Pwgl or the new features of Max 8.3.1. I personally prefer the Bach package, but i know that switching platforms is quite annoying.

Although I don't have a timetable, we are aware of the issue and hope to have a fix in the next update.

Thank you for replies. I can wait for update, hoping the issue is resolved, thanks Ben. @ Riccardo: bach is among my next studies, I think as soon as possible I will convert my OpenMusic algorithmic composition library in that environment. 24h in a day are too few... Many Thanks to everyone.

I have encountered another question with another software and a dmg image file that did not open in El Capitan, discovering that the problem was dued to the new Apple file system APFS (from High Sierra forward), not compatible with HFS or HFS+ old file system.

So, only for sake of curiosity, I was wandering if the problem here exposed was depending by the same issue. Thanks for any answer.

I have encountered another question with another software and a dmg image file that did not open in El Capitan, discovering that the problem was dued to the new Apple file system APFS (from High Sierra forward), not compatible with HFS or HFS+ old file system.
So, only for sake of curiosity, I was wandering if the problem here exposed was depending by the same issue. Thanks for any answer.

Unrelated. the crash happens because Max 8.3 adopted an operating system call (explicitly or implicitly) which is incompatible with osx 10.11. (And presumably they don’t do as rigorous testing on platforms that Apple hasn’t even supported/updated since 3 years ago).

Unrelated.  the crash happens because Max 8.3 adopted an operating system call (explicitly or implicitly) which is incompatible with osx 10.11.  (And presumably they don’t do as rigorous testing on platforms that Apple hasn’t even supported/updated since 3 years ago).  

I have resolved updating to High Sierra, OsX 10.13.6. Now Max saves the new patches without any problem.

Having the same issue with macOS High Sierra 10.13.6 .

I cannot save a new patch ether on 8.3.2, 8.31, 8.3.

Hello, 
Having the same issue with macOS High Sierra 10.13.6  .

I cannot save a new patch ether on 8.3.2, 8.31, 8.3. 

Charles, are you sure your crash is really the same crash? There are just so many ways to crash an app via any given workflow :)

It's probably best to start a new thread and include the crash log (and file a report with support) unless your crash log contains:

Application Specific Information: Crashing on exception: 

+[NSTextField labelWithString:]: unrecognized selector sent to class

Also worth noting that 8.3.2 release notes contain "Save Dialog: fixed crash (MacOS 10.11 only)" which I would have to bet is to address Fabio's original crash (that he worked around by upgrading).

Charles, are you sure your crash is really the same crash?  There are just so many ways to crash an app via any given workflow :)

Application Specific Information: Crashing on exception: +[NSTextField labelWithString:]: unrecognized selector sent to class 0x7fff75c0cc28

Found the reason why, I was using a slash in my folder name destination.. :\ 

Thanks you for your answer @Tyler, i'll create another thread next time I have an Issue.

Found the reason why, I was using a slash in my folder name destination.. :\ 
Oupsi