MuShoo

Trying to figure out if I can run a max standalone app 'headless' - no UI, no windows, etc. Ideally wouldn't even show up in the dock.

Barring that, is there any way to disable the crash reporter dialog for a specific app? I can do the defaults write to turn it off system wide, but that's.... shady. I'm expecting/planning on this app to crash sometimes, and relaunch gracefully (it's controlled by another max standalone), so having it pop up a dialog every time it dies isn't ideal.

Trying to figure out if I can run a max standalone app 'headless' - no UI, no windows, etc. Ideally wouldn't even show up in the dock.
Barri

no-ui-mode-for-standalone-or-disable-crash-window-for-just-one-app

max user interface with thispatcher window messages, and plist edit.

add this key into plist of the standalone :

I also delete everything from the interfaces folder of Standalone,

and make own dsp setup patcher if needed.

defaults write -app "Application Name" NSQuitAlwaysKeepsWindows -bool false

don't forget to delete it's saved state in ~/Library/

I disabled saved state, and any kind of logs, caches, recent items, revisions etc in my OSX

That would need a combination of
max user interface with thispatcher window messages, and plist edit.
add this key into plist of the standalone :
<key>LSUIElement</key>
	<true/>

--------
I also delete everything from the interfaces folder of Standalone,
and make own dsp setup patcher if needed.
crash reporter per app :
defaults write -app "Application Name" NSQuitAlwaysKeepsWindows -bool false

don't forget to delete it's saved state in ~/Library/Saved Application State/

I disabled saved state, and any kind of logs, caches, recent items, revisions etc in my OSX




Well, I tried the defaults write thing - didn't seem to take. I checked with a defaults read in the terminal, and it's definitely activated (NSQuitAlwaysKeepsWindows = 0) but I'm still getting the popup when it crashes. I've gotten away with making a semi-headless app (Haven't tried putting the Agent key into the plist yet) by telling thispatcher to send the window to -50000, -30000, position.

Any thoughts? I'm on High Sierra, maybe that's it?

Ooop, just tossed the LSUIElement key in - no more crash reporter! Thanks much!

Ooop, just tossed the LSUIElement key in - no more crash reporter!  Thanks much!

Just out of curiosity - why do You expect Your app to crash ?

You are welcome.
Just out of curiosity - why do You expect Your app to crash ?


I'd posted an earlier version of it here (it is a tiny piece of a MUCH larger whole), but I've just split it into two parts. Basically, it's a VST validator - scans through an entire folder of VSTs, opening each one in sequence, to check that they can actually open before adding them to a [coll] to populate a menu with. Some plugins would freeze up the scanner, some would outright crash max, so I split it where the main app is handling gathering all the plugins in the folder, keeping track of the valid ones, and various ongoings with [shell], while the secondary headless app actually contains the [vst~] and handles loading and checking for error messages.

This way, the secondary app can crash/lock up (I have a 15 second timeout that kills and relaunches the secondary app), and the main app will just count those plugins as invalid, relaunch the validator, and keep on chugging.

No UI mode for Standalone? Or, disable crash window for just one app?