macos high sierra

[mymkv]

makemkv chrashes short after launch (with or without bluraydisc in drive).

[koenkooi]

Yep, same issue here.

[mechanic57]

I have the same issue. However, I believe this may be due to Apple reverting to a new form of AFP as MKV works fine on a Mac running Sierra or earlier.

[DrBob]

I have the same issue. However, I believe this may be due to Apple reverting to a new form of AFP as MKV works fine on a Mac running Sierra or earlier.

I have the same issue. I've switched back and forth between Sierra and High Sierra Beta 1 & 2 on this machine with the latest version of MakeMKV and the problem only occurs with High Sierra. I do not suspect the new file system because apps generally don't need low levels access to the files, they simply send a request to the operating system which actually saves or reads files. This type of symptom commonly occurs when an app calls a very old API in the operating system that no longer exists. Apple notifies app developers years in advance when they are deprecating old APIs and replacing them with new ones, but every once in a while I run into a piece of software that has this type of glitch because the developer just wasn't paying attention. Lets hope it gets fixed quickly.

I also worry that MakeMKV is still a 32 bit program since Apple has officially notified software developers that all apps must be 64 bit starting in 2018. I'm not sure if they won't run in future versions of macOS or its just an App Store restriction, but either way, MakeMKV should be updated to 64 bit just to avoid problems in the future.

[Woodstock]

Did you enable the new file system with High Sierra?

There have been a number of apps that break with the case-sensitive file names introduced with the new file system, because they cannot find their files.

[koenkooi]

Did you enable the new file system with High Sierra?

There have been a number of apps that break with the case-sensitive file names introduced with the new file system, because they cannot find their files.

Yes, I've changed to APFS. I'm not sure that's the issue, Adobe Lightroom used to crash on case sensitive filesystems and it still works, but adobe might have fixed this after about a decade of pretending it's not a bug...

[DrBob]

Did you enable the new file system with High Sierra?

There have been a number of apps that break with the case-sensitive file names introduced with the new file system, because they cannot find their files.

I've converted to APFS in the Public Beta, I don't expect any file system issues because the Developer Preview was case-sensitive but the Public Beta is supposes too be case-preserving but case-insensitive, so apps that write upper and lower case file names will be able to find their files.

IMHO apps that crash when confronted with case-preserving, case-sensitive filesystems are poorly written apps. If an app requests a file that doesn't exist, macOS will return an ENOENT (“File Not Found”) error code, the app then should notify the user or perform an error recovery procedure at that point, not crash.

macOS has had case-sensitive and case-insensitive versions for years so there is no reason any app should crash when working with those filesystems. I'm going to guess that its a bit more likely that there is some other reason that MakeMKV is crashing on launch.

[mymkv]

starting makemkv inside package:
system writing:

/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-95/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-95/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist'


???

[alex_wants_a_beer]

I, too, am experiencing a fatal error immediately after opening MakeMKV.

I'm guessing Mike is aware, and it is admittedly rather early - nobody is really due a working app until the final release, but it would be quite nice to have an update earlier of course.

I will say that since installing High Sierra this evening, I've been going down my list of 3rd party applications that I always keep installed, opening and activating each app. MakeMKV is the 24th 3rd party application that I installed, and it's the first to fail. But I have about 15 more to go...so we'll see.

So far I'm impressed with High Sierra's beta 3 performance compared to that of iOS 11 beta 3/PB 2. Crash city!!

[T'hain Esh Kelch]

I also worry that MakeMKV is still a 32 bit program since Apple has officially notified software developers that all apps must be 64 bit starting in 2018. I'm not sure if they won't run in future versions of macOS or its just an App Store restriction, but either way, MakeMKV should be updated to 64 bit just to avoid problems in the future.

Apps submitted to the Mac App Store is required to be 64 bit, comming january 1st. As MakeMKV isn't on the Mac App Store, and likely never will be, it is of course not a problem.

High Sierra will allow 32 bit applications to run forever, so until we hit the next macOS release, a 64 bit application is not strictly required.

[DrBob]

Apps submitted to the Mac App Store is required to be 64 bit, comming january 1st. As MakeMKV isn't on the Mac App Store, and likely never will be, it is of course not a problem. High Sierra will allow 32 bit applications to run forever, so until we hit the next macOS release, a 64 bit application is not strictly required.

Notes that I read on Apple's developer site infer that this will be a problem sooner rather than later (i.e. it could be a problem as early as January 2018). Its odd because we will only be halfway through High Sierra's life cycle at that point in time, but that is how the developer note reads. Maybe Apple is trying to get the developers to recompile for 64 nit early to try to minimize the umber of glitches experienced by users. Either way, MakeMKV need to be recompiled for 64 bit so we don't run into trouble, I hope they do it sooner rather than later so we don't get left with an app that doesn't run, just as we are now experiencing with the High Sierra Beta.

[zaborg77]

Hi to everyone. I'm new in this forum and I'm a grateful new user of this software.
I've got the same problem. Since I've installed the first beta of High Sierra and yet now that I've installed the fourth bet the problem remains. I on't know why every time I try to open the software it crashes.

Many thanks. Zaborg77

[Woodstock]

If you can get the crash report data and forward it to support@makemkv.com, Mike will have more to work with. However, like the beta versions of Windows 10, there are a LOT of changes being made in High Sierra that make it incompatible with older programs. Some are deliberate; Others, not. You should also report information to Apple, in case this is one of the "Not" category.

[DJRumpy]

Latest crash mailed off to support. Hopefully it's something simple. Seems like a basic driver issue:

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000216e0000
Exception Note: EXC_CORPSE_NOTIFY

Hopefully something as simple as a DSAPI update or something.

[zaborg77]

Dear Mike,
I'm very glad for your reply. May I ask you help to where I can find the crash report?
In this version of mac I can't understand where I can find the crash report.

Can you help me please?

Many thanks, Zaborg77