Dear Ryohei, On 11/12/2013, at 05:41 , Ryohei SETO wrote:
Hi, The crash happened again due to importing wrong bib file (attached). Now I confirmed with the other machine. As I reported, rebooting stops this behavior (sometime, not always). But after importing bibfiles several times, it may occur again. There should be no crash and on my machine BD never crashes with this bib file. What happens is of course an error, since the bib file is syntactically wrong and needs to be fixed. Once fixed the import/opening works fine. BTW, this has nothing to do with the presence of the field 'eid'. The exported bibfile from Journal of Rheology includes this wrong line "eid = ,”. I often download from this journal’s web site. Each time I have to remove the line by hand. There is no other way unless you inform that journal's webmaster that they are unable to properly export a citation. By the way, some journal uses “eid” instead of “pages”. So far, this field name is not included in BibDesk. It will never be included since AFAIK it does not belong to the BibTeX definition. This has BTW nothing to do with BibDesk and it makes no sense to try to fix mistakes from publishers who ignore well known standards such as BibTeX with another mistake in a software such as BibDesk. Moreover, as I pointed out above, the import problem has nothing to do with the presence of this extra field 'eid'. Once syntactically correct, even the extra field 'eid' is imported and forms part of the record. Regards, Andreas I think it is better to add. Best, Ryohei Seto On Dec 9, 2013, at 7:44 PM, Christiaan Hofman <cmhof...@gmail.com<mailto:cmhof...@gmail.com>> wrote: On Dec 10, 2013, at 1:36, Adam R. Maxwell wrote: On Dec 09, 2013, at 04:09 PM, Christiaan Hofman <cmhof...@gmail.com<mailto:cmhof...@gmail.com>> wrote: On Dec 10, 2013, at 0:54, Adam R. Maxwell wrote: On Dec 09, 2013, at 02:15 PM, Christiaan Hofman <cmhof...@gmail.com<mailto:cmhof...@gmail.com>> wrote: On Dec 9, 2013, at 23:01, Ryohei SETO wrote: https://dl.dropboxusercontent.com/u/9745885/BibDesk_2013-12-09-165629_seto-macbookpro.crash Ryohei 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. Adam Sounds 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 You're right, I forgot about that one. I don't see why that would crash now when it has worked all the time. Christiaan ------------------------------------------------------------------------------ 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 Bibdesk-users@lists.sourceforge.net<mailto:Bibdesk-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/bibdesk-users <BibDesk_2013-12-10-232926_MacBookSana.crash><foo.bib> ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
