Open adib opened 10 years ago
Can you show me the rest of the stack at this point, please?
Finally I figured out how to show the full stack traces...
Those were all the threads that were active when the app froze.
At a glance threads 1 and 9 seems to be calling the main thread when this happens. Wonder if the contention is among those two?
Just thinking out loud, maybe NSDocument
's file coordinator is not setup correctly to handle file packages?
This happens during autosave, NSAutosaveInPlaceOperation
Apparently the bugger is with file coordination. Although nothing else is supposed to be accessing the file package (and for my case, there shouldn't be any since it's in the apps' Application Support folder and not normally accessible directly by the user), [NSDocument saveToURL: ofType: forSaveOperation: completionHandler:
freezes on file coordination and it seems that there's no way to work around it but skipping it altogether.
I have something that's been working OK, will push this out as part of a beta release and see whether there's any negative repercussion for not using NSDocument
's save implementation.
Commit: a216aea61e1f7259841542a22c5b903ed21a6a69
Is calling
[super saveToURL: ofType saveOperation: error]
inside aperformAsynchronousFileAccessUsingBlock
call a good idea?My app sometimes freezes at this point and I wonder if there's a re-entrancy issue here:
I'm on
BSManagedDocument
0.3.x commit f7fc8dcAlso the app has a number of documents open concurrently (different package files of course).