MakeMKV for Monterey Crashes on Second Launch
Posted: Sun Dec 19, 2021 3:54 pm
I have MakeMKV v1.16.5 on an Intel MacBook Pro running on Monterey 12.0.1. It worked fine under Monterey 12.0.0, best I can recall.
MakeMKV launches fine on fresh install. When I launch it a second time it crashes. The behavior is the same whether I go through the process of giving it file/disk permissions through the macOS security mechanism, or no permissions, with disc in the drive or no disc in the drive, with registered or not registered (though, of course, I could not test the first launch with registered). I've tried reading a known, readable disc on first launch, and it goes through all the steps fine.
It seems to be isolated to this behavior on the second launch, where it is trying to download the latest SDF to the ~/Library/MakeMKV folder under my user path.
Once the MakeMKV folder is created in my user Library folder, it crashes on second launch. When I delete this folder, it launches fine, but treats it as an initial launch due to the folder not being there.
The permissions on the folder are the default, as they should be, with my user name having read/write privileges, staff and everyone else having read only privileges.
Any ideas on what is going on, or more importantly, how to resolve it?
MakeMKV launches fine on fresh install. When I launch it a second time it crashes. The behavior is the same whether I go through the process of giving it file/disk permissions through the macOS security mechanism, or no permissions, with disc in the drive or no disc in the drive, with registered or not registered (though, of course, I could not test the first launch with registered). I've tried reading a known, readable disc on first launch, and it goes through all the steps fine.
It seems to be isolated to this behavior on the second launch, where it is trying to download the latest SDF to the ~/Library/MakeMKV folder under my user path.
Once the MakeMKV folder is created in my user Library folder, it crashes on second launch. When I delete this folder, it launches fine, but treats it as an initial launch due to the folder not being there.
The permissions on the folder are the default, as they should be, with my user name having read/write privileges, staff and everyone else having read only privileges.
Any ideas on what is going on, or more importantly, how to resolve it?