Matt Sephton

OK, so I made a discovery. If an app is compressed and starts crashing at launch... simply restart your Mac. After that, the compressed app in question will launch just...

> What does the crash reporter tell about the crash? Or what happens if you launch the application through lldb? Not as much as expected, because: ``` Error Formulating Crash...

> What happens if after the compression of a runnable application you do > ``` > find /path/to/foo.app -depth -exec touch -h -m '{}' ";" > ``` still crashes

I'm fairly confident this is an instance of the same root cause: https://developer.apple.com/forums/thread/696460 more info: https://developer.apple.com/documentation/security/updating_mac_software and the solution is to replace files with new ones (eg. using `ditto`) rather...

I've had an app/binary break recently, repeatedly. Previously, I've recreated the app but in future I'll be sure to investigate more fully. I automatically run afsctool on new additions to...

- PlayOnMac.app approx 1.75 GB - ZLIB -9 compresses to 674.9 MB in 2:26.47 - LZFSE compresses to 621.7 MB in 1:05.79 Results are compressing an app copied fresh out...

No worries! It's an eye-opener, for sure.

Please do, I love a good benchmark. I wonder how much ARM optimisation Apple have done to these algos. I'm betting "a lot"!

> sha256sum of the file is the same after each step and it seems to be in some way actually tied to the file identity. This smells of APFS copy...

Sure thing! I'll probably only use * anyway 😬