Quote:
Originally Posted by odamizu
I tend to think it doesn't make a difference, but for what it's worth, I'm running K4Mac 1.28.0 on High Sierra and using ApprenticeSakuya's patch instead of chmod -x. ApprenticeSakuya's patch eliminates the crash on close that happens with chmod -x.
If K4Mac using chmod -x is getting forced updates, I have to wonder if the crash on close is causing K4Mac to rebuild some of the contents in the Kindle folder, which might include deleting any modified "updates" file or folder, thus allowing the forced updates 
Just wild speculation on my part ... |
I wasn't getting crashes on exit at all (at least with 1.23.1 or lower). It sometimes took a while for K4Mac to shut down when I did cmd Q. Occasionally, it took a while to load as well. Either way, the most likely explanation for that was internet connectivity; every so often it drops out when my partner is using his iPad for something in the cloud in the same room (or he's running a compiler in the home office).
Alternatively, it could be that the sync process is running checks on the app and file components and rebuilding as necessary.
Not to sound paranoid, but my suspicion is that this thread is being monitored...