Jump to content

Crashes too often


Shamango

Recommended Posts

Hi everyone

 

I know that it's quite a common issue, but Logic started crashing so often that I cannot proceed with the current project. Probably it might happen because of some plugins as long as other projects crash much more rarely, but I can't figure out what particular plugins or other problems constitute a cause for crash as I don't know how to properly identify it in the crash log. It can happen anytime, without any actions, and there are some actions that cause crash every time, like insert silence or cmd + ctrl + R.

Attached is the full log text, thank you for any help.

https://drive.google.com/file/d/0B9W0KvTT0z8KSUJqdzBPMWktelE/view?usp=sharing

Link to comment
Share on other sites

In the crash log, near the beginning, the report tells you which thread # crashed.. Scroll down to that, you will see the name several times of one of your plug-ins.. Remove that from 'components' folder.. That works for me..

 

If i have a buggy intermittent plug-in, I want to use.. I initiate it, export audio out.. I then save a channel strip setting for it. I use initials of of song, instrument, patch all in the name.. I also rename the audio region with the channel strip name should I wish to redo it. I then reset the channel strip off..

 

Best to just delete the plug-in, see if their is a new version, and re-install..

Link to comment
Share on other sites

Generally the project is saved at the only internal SSD. I tried to save it at an external HDD, but nothing changes.

 

I'm inclined to blame 3d party plugins. In the crash log the it counts 126 threads. What does this amount stand for?

The first 3d party plugin named in the log is Aphex Vintage Exciter. Also it mentiones Massive and some other plugins. But the most mentioned plugin is Battery 4. Does that mean that every mentioned plugin could be a cause to crash or some are just mentioned? I used these plugins before but there were way less crashes.

I've tried to delete all the plugins that are mentioned in threads list in the log, then try "insert silence" or "cmd + ctrl + R" to test - instant crash (unlike other projects). Finally, I've deleted ALL the component files from Component folder - still the same result. In such moments I'm thinking of switching to another DAW.

 

Also it says:

Crashed Thread: 0 Dispatch queue: com.apple.main­thread

Thread 0 crashed with X86 Thread State (64­bit):

Logical CPU: 2

Error Code: 0x00000004

Trap Number: 14

 

What does it mean?

Link to comment
Share on other sites

Mavericks, not a template, a clean project.

If a plugin is simply disabled in the project, does that mean it is not seen by Logic and does not take any resources or does not affect the system any other way? Or should it be completely deleted from channel strip for that purpose?

Link to comment
Share on other sites

I've found that it instantly crashes when I simply select Drum Machine Designer channel strip in arrangement window. I'm trying to delete it from the mixer, it asks whether I should delete regions on the track, I confirm, but it doesn't delete it and finally crashes so that I couldn't even transfer pieces of the project to a new one. It's kinda hell.
Link to comment
Share on other sites

Yes, it's not the case. I always load saved preferences file when load a project to ensure all midi mappings are in place. I'm just transferring the thing to a new project piece by piece. So much time wasted, don't want to waste more. Apple should do something about this terrible instability which sometimes cost you more than just time and money. Logic is very advanced and attractive, but no other daw crashes so often, there should be some reliable protection.

 

No help with reading crash log details? Can't google out anything constructive on this subject.

Link to comment
Share on other sites

100 steps. Not so many regions. I've got quite powerful machine.

 

I saw the log.

 

Try reducing the Undo steps.

 

There must be something that's eating Logic's memory if you cannot insert silence without crashing.

 

What if you don't load your saved preference just for testing purposes?

Link to comment
Share on other sites

Did you try 'recovery mode'.. Boot up in recovery mode (google to see which keys to hold down while booting up). Recover from Apple.. I'm not sure if Mavericks OS will let you recover..

 

Sometimes, processes in OSX code get corrupt, and Logic references OSX code to do its job.. Recovery will not disturb any of your settings.

 

It's saved me plenty of times..

Link to comment
Share on other sites

I tried entering into recovery mode by pressing Cmd + R while booting up but nothing happens. I've started a new project already, however, I notice that animation and general behavior becomes not quite smooth some time after Logic loading, looks like it's not enough resources which I never experienced before, since I have plenty resources. It all started after the update to 10.2.1.

Would you recommend to go El Captian btw? Maybe that's one of the reasons...

Link to comment
Share on other sites

When you restart, hold down Option. That way you can see if you even have the recovery partition on your HD, otherwise nothing will happen when you press Command R.

 

El Capitan is really optimized for SSD drives, and many people say Logic 10.2.1 works great on it.

Do a Time Machine backup and try it.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...