On Sep 8, 2007, at 11:18, Adam M. Goldstein wrote: > While editing a new publication, BD starting using up all available > processor resources on both cores (!). > > I noticed that the preview stopped working---the "working" indicator > was going around and around, not generating a preview.
We get periodic reports of this, but it's not reproducible on any of my systems. I suspect it's an NSTask issue; when used from a secondary thread, it seems to randomly crap out and lose the connection to its parent process. I had that problem using DataTank, so the developer ditched NSTask and wrote his own fork/exec wrapper. I don't understand why the runloop keeps spinning, though, instead of blocking. We really need access to NSTask's source code to figure it out. If you can find the log file from that TeX run in ~/Library/Caches/ Cleanup at startup (hidden folder), it might have some clues. > It had worked before, though, for the previous publication and all > others I have been using. If you can reproduce it with a particular pub and bst, that would be excellent. > Also, BD continued to work perfectly well the whole time. That's typical. It's a secondary thread that's gone crazy. You may even end up with multiple "BibDesk" processes in Activity Monitor and have to kill them manually. -- Adam ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bibdesk-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
