iMovie Crashing on patched Catalina #2
Comments
|
I noticed the exact same thing, and I have the exact same code:
System:
Crash report
|
|
Macbook Pro 7.1 with Catalina Here is output: Date/Time: 2019-12-24 19:47:08.172 +0100 Time Awake Since Boot: 4900 seconds System Integrity Protection: disabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Termination Signal: Segmentation fault: 11 VM Regions Near 0x10: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 1:: Dispatch queue: com.apple.iLifeMediaBrowser_spotlightGCD Thread 2: Thread 3: Thread 4:: Dispatch queue: com.apple.root.default-qos Thread 5: Thread 6:: com.apple.ProGL.object-deletion Thread 7:: Dispatch queue: Private metadata write queue Thread 8:: Dispatch queue: com.apple.root.background-qos Thread 9:: Dispatch queue: com.apple.Metadata.storeattr Thread 10:: Dispatch queue: com.apple.root.utility-qos Thread 11: Thread 12:: ExtendedAudioFileScheduler::WorkerThreadProc Thread 13:: ExtendedAudioFileScheduler::WorkerThreadProc Thread 14: Thread 15:: MIO Mounting Thread Thread 16:: MIO Mounting Thread Thread 17:: MIO Mounting Thread Thread 18:: com.apple.NSEventThread Thread 19:: AMCP Logging Spool Thread 20: Thread 21: Thread 22:: com.apple.helium-texture-finish Thread 0 crashed with X86 Thread State (64-bit): Logical CPU: 0 Binary Images: External Modification Summary: VM Region Summary: REGION TYPE SIZE COUNT (non-coalesced) ` |
|
Any update on the issue? |
|
@bokie1 the author hasn't commented, I suspect it has something to do with Metal APIs, (there are a few known issues with graphics display due to that). Not sure if its something "fixable", I hope it is! |
|
I had the very same issue on my macbook pro late 2008 on catalina, and also mojave... I have solved this by using older iMovie version 10.1.2 (which I found installed on another macbook at home...). Maybe even newer versions work, but definitely not the latest one... hope this helps someone, I spent 2 days reinstalling like crazy :)) |
|
Thanks to the tip of @lukas700 I installed version 10.1.10 (previously I had 10.1.14 installed), this time iMovie does not crash anymore, but I do have the issue that I can't import any video's in my projectfolder ("not enough disk space"). I will update once I know more. |
|
in my case importing of videos and photos worked just fine, including exporting to a file after finishing my project... |
Same here. As a workaround, I've put the the projectfolder ('Mediathek') on a MacOS Extended (journaled) formatted USB stick. That does the trick. |
|
I'm having the same issues. Where can I find an older version of iMovie? |
|
Anyone been able to resolve or point to where to download older version of iMovie? Happens everytime I try to import media |
Hey @ghasty, DosDude1 posted the version of iMovieto use on a Mac Rumours forum. https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-28471749 |
mrcbax
added
off-topic
|
Your issue has been closed because it is a common problem that can be remedied by taking the appropriate steps or just reading instructions: http://dosdude1.com/catalina/ Your comment has also been closed because it counts as off-topic according to the community guidelines which state that GitHub issues are for code-related problems only. |
Thanks for another great patch!
So I've been using the patcher since the previous version on a 2009 MacBook Pro, only shortly after the Catalina release before attempting to upgrade the OS, there was an update to mostly all Apple apps, including iMovie, and ever since, I could not make it work again. I've tried to do a clean install of Catalina (via bootable installer) however the issue still happens, I'm not sure if it's related to the patch, just would like to know if there's anything that could be done to make it work again. The issue happens only when you create a new project or open an existing one.
Here are the machine details:
and the error stack:
Any idea what may be happening? Any possible workaround or fix?
Thanks in advance!
The text was updated successfully, but these errors were encountered: