Am Mittwoch, 16. Mai 2018 00:10:34 CEST schrieb Scott Kostyshak <skost...@lyx.org>: > On Wed, May 02, 2018 at 04:00:12PM +0000, Scott Kostyshak wrote: > > On Wed, May 02, 2018 at 01:06:04PM +0000, Jean-Marc Lasgouttes wrote: > > > Le 28/04/2018 à 00:06, Scott Kostyshak a écrit : > > > > On Wed, Apr 25, 2018 at 06:41:36PM +0000, Scott Kostyshak wrote: > > > > > > > > > it is not 100% reproducible for me. I wonder if valgrind might be > > > > > useful > > > > > to try in this situation. > > > > > > > > Attached is a valgrind log. Do the invalid reads provide any clues? > > > > > > Does this patch help? I have a more complicated approach, but this should > > > be > > > good enough for now. > > > > With the patch I still get a SIGSEGV. I think the dialog shows and then > > the SIGSEGV immediately occurs. In the attached screenshot, I move the > > SIGSEGV to show that behind it is the dialog. > > I think I am the only one who can reproduce this, right? For those who > cannot reproduce, do you have a clean Valgrind log? > > Scott >
I can reproduce. But I cannot understand, why anyone should use separate lyx instance. Works OK with using 'new lyx-window'. Kornel
Description: This is a digitally signed message part.