constant crashing

[kwiz]

It's possible you're typing too much and getting a character wrong.

Try typing just part of that file name. Find any file will give you all the results matching your string, even if incomplete.

Yeah, I thought that might be the case as well but even inputing only the partial name yielded no results.

[stubbsonic]

Just to mention this for future readers, in Finder, visibility & system weren't in the search menus by default. I chose "Other..." then did a search for both "visibility" and later "System". When the search result came up, there's a check box on the right for "In Menu". Checking that made added it to the main list of options.

[EDIT] Setting visibility to "visible or invisible", and System files "are included, I tried to search .kext, invisible and system, and got 354 results in Finder. I set the modifiers before entering the text, not sure if that makes a difference.

I went to Find any File and searched .kext and got 483 results.

[bayswater]

Just to mention this for future readers, in Finder, visibility & system weren't in the search menus by default. I chose "Other..." then did a search for both "visibility" and later "System". When the search result came up, there's a check box on the right for "In Menu". Checking that made added it to the main list of options.

Using that, I tried to search .kext, invisible and system, and got no results in Finder.

I went to Find any File and searched .kext and got 483 results.

I used EasyFind for that reason. I've had the Finder search fail to find a file that is visible and sitting on the desktop, or even in the window I'm doing the search from, even if I cut and paste the file name from the Finder to the search window.

[kwiz]

Just to mention this for future readers, in Finder, visibility & system weren't in the search menus by default. I chose "Other..." then did a search for both "visibility" and later "System". When the search result came up, there's a check box on the right for "In Menu". Checking that made added it to the main list of options.

Using that, I tried to search .kext, invisible and system, and got no results in Finder.

I went to Find any File and searched .kext and got 483 results.

I used EasyFind for that reason. I've had the Finder search fail to find a file that is visible and sitting on the desktop, or even in the window I'm doing the search from, even if I cut and paste the file name from the Finder to the search window.

Got it! Thanks Bayswater. I won't be able to check again until tomorrow, but when I do, I'll report back.

[bayswater]

I think Mr Stubbs added all the value in that one.

[dix]

Has it been established whether all DP projects crash, or just a specific one? ...maybe I missed it. I don't see this info in previous posts.

[mikehalloran]

It's possible you're typing too much and getting a character wrong.

Try typing just part of that file name. Find any file will give you all the results matching your string, even if incomplete.

Yes, type part, make sure that system and invisible files can be displayed. You may have to disable SIP to view and remove.

Turning Off Rootless System Integrity Protection in OS X El Capitan 10.11 +

1 Reboot the Mac and hold down Command + R keys simultaneously after you hear the startup chime, this will boot OS X into Recovery Mode
2 When the “OS X Utilities” screen appears, pull down the ‘Utilities’ menu at the top of the screen instead, and choose “Terminal”
3 Type the following command into the terminal then hit return:
4 csrutil disable; reboot

5 You’ll see a message saying that System Integrity Protection has been disabled and the Mac needs to restart for changes to take effect, and the Mac will then reboot itself automatically, just let it boot up as normal
You can also issue the command by itself without the automatic reboot like so:

csrutil disable

How to Re-Enable Rootless System Integrity Protection in OS X
Simply reboot the Mac again into Recovery Mode as directed above, but at the command line use the following syntax instead:

csrutil enable

Just as before, a reboot of the Mac is required for changes to take effect.

[kwiz]

I think Mr Stubbs added all the value in that one.

You're right.
Thanks Stubbsonic!

[kwiz]

It's possible you're typing too much and getting a character wrong.

Try typing just part of that file name. Find any file will give you all the results matching your string, even if incomplete.

Yes, type part, make sure that system and invisible files can be displayed. You may have to disable SIP to view and remove.

Turning Off Rootless System Integrity Protection in OS X El Capitan 10.11 +

1 Reboot the Mac and hold down Command + R keys simultaneously after you hear the startup chime, this will boot OS X into Recovery Mode
2 When the “OS X Utilities” screen appears, pull down the ‘Utilities’ menu at the top of the screen instead, and choose “Terminal”
3 Type the following command into the terminal then hit return:
4 csrutil disable; reboot

5 You’ll see a message saying that System Integrity Protection has been disabled and the Mac needs to restart for changes to take effect, and the Mac will then reboot itself automatically, just let it boot up as normal
You can also issue the command by itself without the automatic reboot like so:

csrutil disable

How to Re-Enable Rootless System Integrity Protection in OS X
Simply reboot the Mac again into Recovery Mode as directed above, but at the command line use the following syntax instead:

csrutil enable

Just as before, a reboot of the Mac is required for changes to take effect.

Hey Mike, unfortunately, none of the suggestions worked.
Really not sure why, I followed all the instructions to the letter but I couldn’t get Easy Find, the Finder, and Find any file to find the file that you suggested I delete. Weird thing is, all of the aforementioned file finders will find anything else I input; invisible and otherwise.
Thanks again for everyone’s help but I’m throwing in the towel and erasing the drive and doing a fresh install on everything that I need. Thank God it’s not my main studio rig, I’d be in real trouble if that were the case.

[Kurt Cowling]

I know you guys are waist deep in stuff that I don’t understand but, I was having lots of random (no discernible pattern) hangs. On a hunch I disabled auto-save in DP prefs and have had very few issues since then. Just a thought...

[HCMarkus]

I know you guys are waist deep in stuff that I don’t understand but, I was having lots of random (no discernible pattern) hangs. On a hunch I disabled auto-save in DP prefs and have had very few issues since then. Just a thought...

Although it hasn't happened to me recently, I, too, suspect that Auto-Save may be a cause of crashes. It seems that, if one happens to take an action within DP at the exact moment the Auto Save is initiated, trouble can result.

But I still have it enabled, as it has saved my tucas too many times.

Thanks again for everyone’s help but I’m throwing in the towel and erasing the drive and doing a fresh install on everything that I need. Thank God it’s not my main studio rig, I’d be in real trouble if that were the case.

Kwiz, so sorry you are gonna' have to start from scratch. Once you get it put back together, may I suggest you do what I have taken to doing: clone the working boot drive periodically and keep the clone as a backup. I started doing this after I encountered an issue with a low-level MOTU driver that required me to build a new boot drive from scratch to get my 828ES working properly. Now, whenever I add more than a couple of plug-ins or VIs to my system, I re-clone the boot drive to a spare SSD using SuperDuper. I may never need it, but if I do, I'll be very thankful to have it.

Good luck!

[stubbsonic]

Now that I have just gone through my "clean install of 2021" (seems like a good year for a fresh start) I am going to make a clone. My system seems clean as a whistle and is running very reliably.

I don't know what the down-sides are, if I was to ever use a clone (from Carbon Copy Cloner) as a basis for restoring a damaged boot drive. I suppose Time Machine is doing all of this, but for some reason, I have a harder time relating to how to use Time Machine in a "crisis".

Thanks, Kurt, for mentioning the auto-save thing. It's a good point. I'll definitely give that a try if I ever get into rough waters.

[bayswater]

I know you guys are waist deep in stuff that I don’t understand but, I was having lots of random (no discernible pattern) hangs. On a hunch I disabled auto-save in DP prefs and have had very few issues since then. Just a thought...

I have it enabled and rarely notice it is happening. Is it possible the drive you save to has gone into some sort of sleep mode, and it's taking time for the save process to wake it up?

[kwiz]

I know you guys are waist deep in stuff that I don’t understand but, I was having lots of random (no discernible pattern) hangs. On a hunch I disabled auto-save in DP prefs and have had very few issues since then. Just a thought...

Although it hasn't happened to me recently, I, too, suspect that Auto-Save may be a cause of crashes. It seems that, if one happens to take an action within DP at the exact moment the Auto Save is initiated, trouble can result.

But I still have it enabled, as it has saved my tucas too many times.

Thanks again for everyone’s help but I’m throwing in the towel and erasing the drive and doing a fresh install on everything that I need. Thank God it’s not my main studio rig, I’d be in real trouble if that were the case.

Kwiz, so sorry you are gonna' have to start from scratch. Once you get it put back together, may I suggest you do what I have taken to doing: clone the working boot drive periodically and keep the clone as a backup. I started doing this after I encountered an issue with a low-level MOTU driver that required me to build a new boot drive from scratch to get my 828ES working properly. Now, whenever I add more than a couple of plug-ins or VIs to my system, I re-clone the boot drive to a spare SSD using SuperDuper. I may never need it, but if I do, I'll be very thankful to have it.

Good luck!

Thanks HC that's great advice, and I'll be sure to do that!
I'm still in install mode but at least this time I can really streamline my SSD since some of the programs that I had installed, I no longer use.
The bummer is installing my entire NI Komplete library again. Even though I have all the content on a separate HD, NI requires you to re-install everything, programs and content. SMH
With all that said, at least I'm not crashing anymore...lol

[stubbsonic]

The bummer is installing my entire NI Komplete library again. Even though I have all the content on a separate HD, NI requires you to re-install everything, programs and content. SMH

I just did a fresh install and Native Access definitely gave me the option to "Locate" the libraries, so I did NOT have to download them. Hopefully you catch this before you've gotten in too deep.