Auto backup ?causing lockup?

:smiley: First the rave review; Scrivener
Because the Tutorial is so very Professional, complete, comprehensive, clear, comprehendible, those are the reasons that I am using Scrivener rather than one of the many other “writer’s program”s that I have demo’d. Seriously, the tutorial deserves 10 of 10 gold stars.

Prices range from “$0” to $150 for programs, and for what it does Scrivener’s $45 price is a great value, especially with the tutorials that are included. Personally, I’m not waiting for some special deal somewhere to ‘get it cheap’, it is well worth the $45.

IN ADDITION:
ok! There are graphics imbedded in the “draft” folder in the Tutorial, but this isnt covered in the tutorial, good question for the website, how are these graphics dealt with when its time to “publish”?

:open_mouth: I have come upon one irritating problem, cant seem to figure it out:

PROBLEM: one system wide lock out, 4 program “fails to respond” and force to quit.
once when adding a quicktime to Reference folder, 4 when Scrivener begins save to backup and zip. (3 x on auto save at close, and one when manually call for backup.)
Also: the manual backup was initiated after repair permissions was done.
Also: there are 4 other backed up and zipped files in this folder, tutorial and testing files. Had no problem with them.
TEMP Solution: turn off auto backup and do not use back up.

Obvious question before the experts step in: how long did you wait during the backup process before initiating force-quit? Is it possible it just hadn’t finished yet?

Another, possibly also obvious, question: were there any errors listed in Console?

How large is this QuickTime file? nom may have a good point, if it’s a 5gb movie file than it may take quite some time to both duplicate and zip compress. You might consider disabling zip compression in the Backup preferences tab, but really if you’ve got a research file that big, I’d suggest looking at the File/Import/Research Files as Aliases menu command, and link those things into the project instead of importing them.

Alternative problem: the QuickTime file might be mildly corrupted. If it isn’t that huge, it could still be causing issues. How does your project backup with this file in it? Corrupted movies can manifest as frozen interfaces, spinning pizza wheels, or just outright crashing.

And yes, do post anything you get on the console. Use the Scrivener/Reveal Support Folder in Binder menu command and paste the contents of the Console.log file, inside the Logs folder. There is one other potential problem: a damaged zip library in your operating system. Disabling zip compression mode would instantly clear up the problem, and console would very likely have info on its failure if this is the problem.

waited ten minutes, no-- it was locked up not just taking a while.
next time I left out the QT file, still over 10 minutes wait, and still not “finished”

:neutral_face: Answer seems to be Time Machine, by some odd coincident TM was backing up at the same time, (each time) normally this is not a conflict. Apparently the “save and compress” was taking some of the “same space” as TM or something else that I don’t understand. I noticed that both TM & Sr were not ‘finishing’ / that lead me to a “hmm” moment.

Bottom line; I turned off TM, just go to the bar and select ‘back up now’ occasionally, I really don’t need an hourly back up. With TM OFF, no problem, I select ‘back up now’ & Srivener backs up with zip, I verify the file, and does it in less than a minute.
:wink:

other note; I don’t understand why Apple has TM with out any controls, I mean this is a Mac, not a widows machine, I am not concerned about a crash “just any moment”


No kidding, I’d love to be able to set the interval. I really look at TM as being more of a personal undo than a system repair tool—though I have used it as one of those as well. You never know when a crash is going to happen; when a hard drive is going to fail. Having the assurance of being able to restore your system to at least one hour away from where you were last is pretty nice. I had to restore a laptop once that had a failed drive. TM brought it almost precisely up to the spot where the drive started to die in one single move. On the other hand, as long as you can remember to “Back Up Now” periodically (especially once before you shut down for the day, as that last backup is the one TM will save all down the line), it’s in a way superior since you are calling the milestones, rather than the rotation of the earth.

At any rate, I’ve never run into this precise problem. The system certainly does run more slowly while TM is running, but usually it just flickers on and off throughout the day as most of my work is text based—it would be hard to hit it while running even if I was trying. So I might not be a good test subject.