On Dec 09, 2013, at 04:09 PM, Christiaan Hofman <[email protected]> wrote:
On Dec 10, 2013, at 0:54, Adam R. Maxwell wrote:On Dec 09, 2013, at 02:15 PM, Christiaan Hofman <[email protected]> wrote:
On Dec 9, 2013, at 23:01, Ryohei SETO wrote:
https://dl.dropboxusercontent.com/u/9745885/BibDesk_2013-12-09-165629_seto-macbookpro.crashRyohei
Weird one. There does not seem to be anything specific to the problem in that crash report. Some generic crash when closing a file read.
I'd never seen EXC_GUARD before, and the fade2dead address looked interesting. With a bit of searching, it turns out this is a close on a guarded file descriptor (Greg Parker is an Apple engineer):
https://twitter.com/gparker/status/395678654375546881
There should be an +[NSPipe pipe] somewhere to create that autoreleased NSConcretePipe, but I don't recall anything in the cmd-shift-L code path that would do it.
AdamSounds more like something in the system being messed up. We only open the file indirectly by reading a string from it. And the parsing is the same as when you drop the file or paste the bibtex, and that all gives just the warning. Also given the tweets, it really seems more like a system bug. Otherwise something completely unrelated that just pops up here for some vague reason. It really does not look like anything related to our code related to anything of this.
I wouldn't rule out an OS bug, but does this run through the NSPipe code that I had in NSData category? Looks like you moved it to the parser, but it's an obvious NSPipe call when you try and parse bibtex data that's not a file.
adam
------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
