On Mon, Feb 06, 2023 at 03:19:15PM +0100, Jean-Marc Lasgouttes wrote: > Le 06/02/2023 ?? 15:02, Jean-Marc Lasgouttes a écrit : > >Le 06/02/2023 ?? 13:32, Pavel Sanda a écrit : > >>>Unfortunately valgrind changes speed of painting and I can't reproduce > >>>it then. > >>>But I am able to run it with any lyxer debug ouput or check potential > >>>patch > >>>if you have some idea... > >> > >>JMarc, do you have idea for a potential patch? P > > > >You are wise to ping me, I forgot about this one. > > > >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 (1246): validate() -> build() insets/InsetInfo.cpp (780): metrics() -> build() insets/InsetInfo.cpp (780): metrics() -> build() insets/InsetInfo.cpp (780): metrics() -> build() insets/InsetInfo.cpp (780): metrics() -> build() insets/InsetInfo.cpp (780): metrics() -> build() insets/InsetInfo.cpp (780): metrics() -> build() insets/InsetInfo.cpp (780): metrics() -> build() insets/InsetInfo.cpp (780): metrics() -> build() insets/InsetInfo.cpp (780): metrics() -> build() insets/InsetInfo.cpp (780): metrics() -> build() insets/InsetInfo.cpp (780): metrics() -> 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 Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
