On Mon, Feb 06, 2023 at 03:50:40PM +0100, Pavel Sanda wrote: > > >One solution would be high-level, like "forbid screen redraws while some > > >inset is the unstable state" (this is _expected_ to be a very transient > > >situation. > > > > > >Other solution would be very local and try to avoid these regenerations of > > >info insets (maybe just mark as dirty and regenerate on demand). > > > > Could you try to apply this patch and tell me what debug message you obtain? > > I expect the last one will be validate->build. > > Indeed: > insets/InsetInfo.cpp (1246): validate() -> build() > .... (zilion times) > insets/InsetInfo.cpp (1246): validate() -> build() > insets/InsetInfo.cpp (780): metrics() -> build() > insets/InsetInfo.cpp (1246): validate() -> build() > .... (zilion times) > insets/InsetInfo.cpp (1246): validate() -> build() > > lyx: SIGSEGV signal caught! > ... > > > > > Do you have the code pane open? > > No. > > > I wonder why validate is called. Maybe previews generation. > > Yes I do have previews on. Also the crash needs my mouse cursor > moves above LyX window to trigger this (maybe the action triggered > by cursor gliding over inset info?) > > I think I found another way how to trigger the crash: > 1. move your cursor on the changes japanese related changes. > 2. go to the gui prefs and check(or uncheck) end of paragraph > markers in display pane, click Ok > 3. kaboom
I can confirm that both crashes seem to be gone with 00c39208ac65. Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
