TDEL2 Posted May 17, 2021 Share Posted May 17, 2021 Hi All, I am running into issues trying to open a specific Logic project that crashes Logic immediately upon attempting to open the project. I've already tried the following: (1) Disable core audio (2) open previous / backed up versions (ALL versions of the project crash Logic) (3) creating a new/blank project and importing the old project (selecting the project in the librarian crashes Logic as well) The project in question is a few years old (2017), but was a true labor of love and I'd hate to lose it. Part of me wonders if it's potentially a permissions issue (the file has been backed up on two external drives, and I did have some permissions issues on those drives recently). I have not yet reset those permissions. My understanding is that the current version of Mac OS X does not permit resetting permissions on the system drive itself. All other Logic X projects open without issue - the problem is limited to this single project. For that reason, I'm assuming the issue lies with the project file and not Logic X as a whole, but I can't be sure. I have copied what appear to be the relevant portions of the crash report below. Any help or suggestions would be greatly appreciated. Process: Logic Pro X [2170] Path: /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X Identifier: com.apple.logic10 Version: 10.6.2 (5437) Build Info: MALogic-5437000000000000~2 (10U141) App Item ID: 634148309 App External ID: 841256562 Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Logic Pro X [2170] User ID: 502 Date/Time: 2021-05-17 10:58:22.905 -0500 OS Version: Mac OS X 10.15.7 (19H1030) Report Version: 12 Bridge OS Version: 3.0 (14Y908) Anonymous UUID: 46129172-B2C9-3D56-7147-7E3F9C2748E0 Sleep/Wake UUID: 0673710A-A8FA-4F07-9330-34CE7CC126C9 Time Awake Since Boot: 5500 seconds Time Since Wake: 3000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [2170] VM Regions Near 0x8: --> __TEXT 000000010ef87000-00000001110e3000 [ 33.4M] r-x/r-x SM=COW /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X Application Specific Information: Dublin | 6b34edbe1e2428234532a9a90f0dda622834cd344de3e01f645f6cf5be04bce1 | 781cc937bdf8fcedde9f5ae075d75e80eb832333 | 2021-04-20_07:21:15 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.apple.logic10 0x00000001106f5064 0x10ef87000 + 24567908 1 com.apple.logic10 0x00000001107039f1 0x10ef87000 + 24627697 2 com.apple.logic10 0x0000000110707c9f 0x10ef87000 + 24644767 3 com.apple.logic10 0x000000011070c16f 0x10ef87000 + 24662383 4 com.apple.logic10 0x000000010fbc661e 0x10ef87000 + 12842526 5 com.apple.logic10 0x000000010fb62055 0x10ef87000 + 12431445 6 com.apple.logic10 0x000000010fb6228e 0x10ef87000 + 12432014 7 com.apple.AppKit 0x00007fff318f8fd1 -[NSDocument _initWithContentsOfURL:ofType:error:] + 172 8 com.apple.AppKit 0x00007fff318f8eba -[NSDocument initWithContentsOfURL:ofType:error:] + 231 9 com.apple.AppKit 0x00007fff319676c1 -[NSDocumentController makeDocumentWithContentsOfURL:ofType:error:] + 619 10 com.apple.logic10 0x0000000110416bf4 0x10ef87000 + 21560308 11 com.apple.AppKit 0x00007fff31b6d3db -[NSDocumentController(NSDeprecated) openDocumentWithContentsOfURL:display:error:] + 783 12 com.apple.logic10 0x000000011098773b 0x10ef87000 + 27264827 13 com.apple.Foundation 0x00007fff369c1935 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7 14 com.apple.Foundation 0x00007fff369c1856 -[NSBlockOperation main] + 80 15 com.apple.Foundation 0x00007fff369c17f1 __NSOPERATION_IS_INVOKING_MAIN__ + 17 16 com.apple.Foundation 0x00007fff369c0a23 -[NSOperation start] + 722 17 com.apple.Foundation 0x00007fff369c0749 __NSOPERATIONQUEUE_IS_STARTING_AN_OPERATION__ + 17 18 com.apple.Foundation 0x00007fff369c0619 __NSOQSchedule_f + 182 19 libdispatch.dylib 0x00007fff6e3992b9 _dispatch_block_async_invoke2 + 83 20 libdispatch.dylib 0x00007fff6e38d658 _dispatch_client_callout + 8 21 libdispatch.dylib 0x00007fff6e398cab _dispatch_main_queue_callback_4CF + 936 22 com.apple.CoreFoundation 0x00007fff34385961 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9 23 com.apple.CoreFoundation 0x00007fff34345767 __CFRunLoopRun + 2028 24 com.apple.CoreFoundation 0x00007fff3434491e CFRunLoopRunSpecific + 462 25 com.apple.HIToolbox 0x00007fff32f70abd RunCurrentEventLoopInMode + 292 26 com.apple.HIToolbox 0x00007fff32f707d5 ReceiveNextEventCommon + 584 27 com.apple.HIToolbox 0x00007fff32f70579 _BlockUntilNextEventMatchingListInModeWithFilter + 64 28 com.apple.AppKit 0x00007fff315b7039 _DPSNextEvent + 883 29 com.apple.AppKit 0x00007fff315b5880 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352 30 com.apple.logic10 0x0000000110990630 0x10ef87000 + 27301424 31 com.apple.AppKit 0x00007fff315a758e -[NSApplication run] + 658 32 com.apple.AppKit 0x00007fff31579396 NSApplicationMain + 777 33 com.apple.logic10 0x000000010fb36b5d 0x10ef87000 + 12254045 34 libdyld.dylib 0x00007fff6e3e6cc9 start + 1/ Quote Link to comment Share on other sites More sharing options...
triplets Posted May 17, 2021 Share Posted May 17, 2021 Do you have a copy of an earlier Logic app version? Like 10.6.1 or 10.5.1? Could be related to 10.6.2 and 3rd party plugins. Quote Link to comment Share on other sites More sharing options...
TDEL2 Posted May 17, 2021 Author Share Posted May 17, 2021 Thanks for the quick reply. I do not have an earlier version of Logic installed. I run 10.6.2. I may have an earlier version on my external drives. Would you suggest trying to open inside an earlier version of Logic? Quote Link to comment Share on other sites More sharing options...
triplets Posted May 17, 2021 Share Posted May 17, 2021 Yup, try to open the project with an earlier version. Quote Link to comment Share on other sites More sharing options...
fisherking Posted May 17, 2021 Share Posted May 17, 2021 you could also try importing everything into a new project... Quote Link to comment Share on other sites More sharing options...
TDEL2 Posted May 17, 2021 Author Share Posted May 17, 2021 you could also try importing everything into a new project... Thanks. I've already tried this, but I am unable to select any version of the old project in the All Files browser without Logic crashing. Quote Link to comment Share on other sites More sharing options...
TDEL2 Posted May 17, 2021 Author Share Posted May 17, 2021 Yup, try to open the project with an earlier version. I tried to open the project in Logic 10.3.3, 10.4.8 and 10.6.0. Unfortunately, the same result. Quote Link to comment Share on other sites More sharing options...
fisherking Posted May 17, 2021 Share Posted May 17, 2021 you could also try importing everything into a new project... Thanks. I've already tried this, but I am unable to select any version of the old project in the All Files browser without Logic crashing. sorry, i missed that. is the project on the same drive as the others? either way, try duplicating it in the finder, then moving (say, to the desktop). then try to open it there... also, you could try importing only select elements of the original into a 'virgin' project, see if anything imports; could be a long process, but if the project's important... try that. Quote Link to comment Share on other sites More sharing options...
TDEL2 Posted May 17, 2021 Author Share Posted May 17, 2021 Thanks. I've already tried this, but I am unable to select any version of the old project in the All Files browser without Logic crashing. sorry, i missed that. is the project on the same drive as the others? either way, try duplicating it in the finder, then moving (say, to the desktop). then try to open it there... also, you could try importing only select elements of the original into a 'virgin' project, see if anything imports; could be a long process, but if the project's important... try that. Yes, it is on the same drive as the other projects. I tried to create a duplicate of the project on the desktop and open it from there. Unfortunately, no luck. I am able to right click on the project, then go Show Package Contents > Media > Audio Files and select the individual audio files without issue. The individual audio files play just fine in iTunes when selected. Is there another method to importing into a "new" project other than using the All Files browser? As mentioned, I can't even click on the project in the All Files browser without Logic crashing. Because of that I am unable to see the contents/elements that might be able to be imported. This was a ~90 track project, so that could be quite a bit of work! Quote Link to comment Share on other sites More sharing options...
fisherking Posted May 17, 2021 Share Posted May 17, 2021 have you tried importing from file>import>logic projects? there you can select things individually, collectively... you have a lot of control over what you import. it's the only way i've ever brought in content from one project into another. Quote Link to comment Share on other sites More sharing options...
TDEL2 Posted May 17, 2021 Author Share Posted May 17, 2021 have you tried importing from file>import>logic projects? there you can select things individually, collectively... you have a lot of control over what you import. it's the only way i've ever brought in content from one project into another. I just tried this - when trying to import from file>import>logic projects, the moment I double click the affected project, Logic crashes. Quote Link to comment Share on other sites More sharing options...
fisherking Posted May 17, 2021 Share Posted May 17, 2021 try rebooting in safe mode. then reboot normally. try disconnecting your audio interface, then open logic using built-in audio. or disable core audio (in logic's audio preferences), then try opening the damaged project. i'd keep trying various things, if the project's important. and perhaps someone else has ideas? good luck with this Quote Link to comment Share on other sites More sharing options...
TDEL2 Posted May 17, 2021 Author Share Posted May 17, 2021 try rebooting in safe mode. then reboot normally. try disconnecting your audio interface, then open logic using built-in audio. or disable core audio (in logic's audio preferences), then try opening the damaged project. i'd keep trying various things, if the project's important. and perhaps someone else has ideas? good luck with this Thanks for your efforts - I’ve already disconnected the audio interface and disabled core audio to no avail. I’ll keep trying various possible solutions. Is anyone able to interpret the crash log above? Quote Link to comment Share on other sites More sharing options...
triplets Posted May 17, 2021 Share Posted May 17, 2021 Is there an app or something called Dublin? It's specified in the crash report. Quote Link to comment Share on other sites More sharing options...
TDEL2 Posted May 17, 2021 Author Share Posted May 17, 2021 There is the Dublin Delay guitar effect that is stock in Logic. That may have been used on this project. But I would presume bypassing all effects would have eliminated that as a cause? Quote Link to comment Share on other sites More sharing options...
triplets Posted May 17, 2021 Share Posted May 17, 2021 Bypassing still reads the plugin. You'd have to remove it from the channel strip when you start that project with core audio disabled. Save the project, close it, and re-open. I would try it first with a copy of course. Quote Link to comment Share on other sites More sharing options...
des99 Posted May 17, 2021 Share Posted May 17, 2021 (edited) Likely the project is corrupted, which is why Logic crashes when trying to open it. This is nothing to do with plugins, this is Logic crashing hard when loading the project: Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008 Exception Note: EXC_CORPSE_NOTIFY As evidenced by the fact Logic crashes when loading it even with the audio engine turned off, and plugins aren't even loaded in this case. Unfortunately, there don't seem to be any tools to fix damaged projects, and the Logic file format is undocumented, and full of compressed binary data that's basically undecipherable, so there's little chance of fixing it. I'd look inside the folder/package to see if there are any auto-backup versions, and try to open those (it looks like you've already tried this though). If not, you might have other regular backups of your work elsewhere (which should be standard practice for important data) so if you were backing up your work appropriately, even with Time Machine, you might be able to find an earlier version that opens and at least rescue what you can. There's not really much else to suggest... Edited May 17, 2021 by des99 Quote Link to comment Share on other sites More sharing options...
TDEL2 Posted May 17, 2021 Author Share Posted May 17, 2021 Bypassing still reads the plugin. You'd have to remove it from the channel strip when you start that project with core audio disabled. Save the project, close it, and re-open.I would try it first with a copy of course. But how would I remove it from the channel strip when I can’t even get the project to open? Do you mean open a blank project with core audio disabled and all effects removed and then try to import? Quote Link to comment Share on other sites More sharing options...
TDEL2 Posted May 17, 2021 Author Share Posted May 17, 2021 Likely the project is corrupted, which is why Logic crashes when trying to open it. This is nothing to do with plugins, this is Logic crashing hard when loading the project: Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008 Exception Note: EXC_CORPSE_NOTIFY Unfortunately, there don't seem to be any tools to fix damaged projects, and the Logic file format is undocumented, and full of compressed binary data that's basically undecipherable, so there's little chance of fixing it. I'd look inside the folder/package to see if there are any auto-backup versions, and try to open those. If not, you might have other regular backups of your work elsewhere (which should be standard practice for important data) so if you were backing up your work appropriately, even with Time Machine, you might be able to find an earlier version that opens and at least rescure what you can. There's not really much else to suggest... Thanks for this information. I regularly backed up to Time Machine, but that’s the odd thing: every backup of this project (daily over a 50 day period) crashes Logic. It’s as if every single version of the project became corrupted somehow. Quote Link to comment Share on other sites More sharing options...
des99 Posted May 17, 2021 Share Posted May 17, 2021 It might have been corrupted early on in it's life, so it's spread and possibly got worse over time. You could try zipping it up and uploading it here (no audio) - maybe an early version and a later version - and we can try to open it, but I don't expect much success... Quote Link to comment Share on other sites More sharing options...
des99 Posted May 17, 2021 Share Posted May 17, 2021 Honestly, in this day and age it's still remarkably frustrating, and somewhat incredible, that a pro app like Logic can corrupt user data on a regular-ish basis (given all the numbers of times people here have had irretrievably corrupted projects) and not load a project at all. And certainly for an app to *crash* when loading project files is also pretty bad. Data should be checked on loading and stuff that's not in the expected format should fail gracefully, or that section of data should be skipped (with a warning), but for the app to crash, rendering everything in that project unusable, is just bad... If you know this is a thing that the app can do, then at least give us a hardened import feature which could retrieve good data from files that otherwise don't load properly, rather than just run the same blind "load the objects from the file directly into memory" thing Logic does, leading to hard crashes with corrupt projects. Do Cubase, Pro Tools or Reaper users get in situations where their projects are corrupted and can no longer be opened? Quote Link to comment Share on other sites More sharing options...
TDEL2 Posted May 17, 2021 Author Share Posted May 17, 2021 I agree completely. I'm not sure how a problem like this is possible on a piece of professional-grade software that has been in continuous development for the better part of 17 years. On the off chance that any of you have a moment to try to open the project on your side, I've attached a .zip file of one of the early project versions below. I removed all audio files to get it down to a reasonable upload size. Thanks again, everyone, for the suggestions and tips. Broken Leaves - Guide Mastered Draft.zip Quote Link to comment Share on other sites More sharing options...
des99 Posted May 17, 2021 Share Posted May 17, 2021 No luck here, I tried a few secret handshake type things which have been known to rescue some things in the past, but it's the parsing of the ProjectData contents that fails, in all four copies of it in that project (even though they are not identical), in both 10.4.x and 10.5.x. I get the exact same crash in all cases. The silly thing is, it could be as little as one byte that's causing it to fail to load, which could be easily fixed if you knew where to look. I'm sure the devs have tools to analyse the project file, but it's just not practically possible for a third-party to do this beyond extracting some basic stuff (I've tried). It seems this project was saved from LPX 10.0.7, a very early version, for someone that still has a copy, it might be worth trying to open it in that on the offchance. Quote Link to comment Share on other sites More sharing options...
TDEL2 Posted May 17, 2021 Author Share Posted May 17, 2021 Well, that’s a serious bummer. Thanks for giving it a go. Out of curiosity, how were you able to determine the ProjectData file is the culprit? Maybe this is the universe telling me to go write new music instead. Edit: I just located a copy of LPX 10.0.7 on a backup from 2014. Will give it a try. Quote Link to comment Share on other sites More sharing options...
des99 Posted May 17, 2021 Share Posted May 17, 2021 One of the things I sometimes try is to transplant bits of non-working projects into working empty projects, to see if I can identify what data Logic is choking on. ProjectData is the main data for the project though, and if this can't be parsed, there's very little chance of opening it. Sometimes though this data is good and it's some other data that's causing the crash (eg corrupt undo data, or a damaged plist file or something). Quote Link to comment Share on other sites More sharing options...
TDEL2 Posted May 17, 2021 Author Share Posted May 17, 2021 Ok, so a small breakthrough. I am able to import project data into LPX 10.0.7… Quote Link to comment Share on other sites More sharing options...
fisherking Posted May 17, 2021 Share Posted May 17, 2021 Ok, so a small breakthrough. I am able to import project data into LPX 10.0.7… as des99 said. nothing i tried worked either. so it's GREAT you could import into an earlier logic. save it, then try importing (or opening) from a newer logic... and let us know how it goes. Quote Link to comment Share on other sites More sharing options...
TDEL2 Posted May 18, 2021 Author Share Posted May 18, 2021 Update: I was able to import virtually the entire project into LPX 10.0.7. Saved it as a new project to my desktop. Tried to open it in LPX 10.6.2 and …SUCCESS. Saved it as a new project there and we are back up and running. There were a handful of small things lost in the transition, but about 95% of the original project is intact. Thanks again for all the help! This forum is excellent. Quote Link to comment Share on other sites More sharing options...
fisherking Posted May 18, 2021 Share Posted May 18, 2021 Update: I was able to import virtually the entire project into LPX 10.0.7. Saved it as a new project to my desktop. Tried to open it in LPX 10.6.2 and …SUCCESS. Saved it as a new project there and we are back up and running. There were a handful of small things lost in the transition, but about 95% of the original project is intact. Thanks again for all the help! This forum is excellent. truly excellent news... glad you stayed with it! Quote Link to comment Share on other sites More sharing options...
triplets Posted May 18, 2021 Share Posted May 18, 2021 Update: I was able to import virtually the entire project into LPX 10.0.7. I wish there was some way to communicate to all Logic users the importance of keeping older Logic versions for this specific scenario. Congrats!! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.