Re: Closing LyX Version 2.1.0beta2,(10 November 2013)

[Mike]

Using the menu system I close all, then quit Lyx. Using command+q Lyx has not crashed once through 3 attempts to reproduce the crash. Loaded two files (master + child); tried a further 3 times to reproduce the crash; there was no crash this morning. However, trying out the find/replace advanced settings now causes Lyx to stall, resulting in a blank work-area in Lyx, then choosing 'force quit', on close Lyx throws up a dialog box asking me if I want to create a new document! Then, choosing no, it closes normally with no crash report. Mike Stephan Witt 2 December 2013 11:02 I'm not aware of any changes, except the unicode/iconv handling. There are two bugs on LyX trac filed: http://www.lyx.org/trac/ticket/8637 http://www.lyx.org/trac/ticket/8287 These issues are not consistently reproducible. Therefor I'm not sure if the crash is not happen with beta1. @Mike: What are you referring to with "using the menu system to close it down" exactly? Does this mean it doesn't crash when exiting with Command-q? Stephan Vincent van Ravesteijn 2 December 2013 08:26 Mike responded privately to say that this didn't happen with beta1.   Stephan ? Any idea ?   Does this involve mime types ? Did something change in this area lately ?   Vincent Vincent van Ravesteijn 2 December 2013 07:42 I am using LyX Version 2.1.0beta2 (10 November 2013) on an Apple Macbook Pro: Processor  2.4 GHz Intel Core 2 Duo; Memory  4 GB 1067 MHz DDR3. On closing the programme using the menu system to close it down, the following dialog window appears:  SIGSEGV signal caught! A problem report generated by the Macbook Pro is attached. Regards, Mike   Does this happen with beta1 as well ?   Vincent  Mike 1 December 2013 19:23 I am using LyX Version 2.1.0beta2 (10 November 2013) on an Apple Macbook Pro: Processor  2.4 GHz Intel Core 2 Duo; Memory  4 GB 1067 MHz DDR3. On closing the programme using the menu system to close it down, the following dialog window appears:  SIGSEGV signal caught! A problem report generated by the Macbook Pro is attached. Regards, Mike