<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Crash swlo!SwTableBox::getRowSpan" href="https://bugs.documentfoundation.org/show_bug.cgi?id=132262#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Crash swlo!SwTableBox::getRowSpan" href="https://bugs.documentfoundation.org/show_bug.cgi?id=132262">bug 132262</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to Julien Nabet from <a href="show_bug.cgi?id=132262#c2">comment #2</a>) > On pc Debian x86-64 with master sources updated today + gen rendering, I > don't reproduce the crash. > Perhaps Windows only. > > A lot of these kinds of logs: > warn:sw.layout:10246:10246:sw/source/core/layout/tabfrm.cxx:892: Cannot > remove in-use Follow Flow Line > warn:legacy.osl:10246:10246:sw/source/core/layout/tabfrm.cxx:885: There > should be a flowline in the follow > warn:legacy.osl:10246:10246:sw/source/core/layout/tabfrm.cxx:1360: Joining > follow flow line > warn:legacy.osl:10246:10246:sw/source/core/layout/tabfrm.cxx:2673: debug > assertion: <SwTabFrame::MakeAll()> - format of table lowers suppressed by > fix i44910 > warn:sw.layout:10246:10246:sw/source/core/layout/tabfrm.cxx:1638: > LoopControl_2 in lcl_RecalcRow: Stage 1! > warn:legacy.osl:10246:10246:sw/source/core/layout/tabfrm.cxx:5660: > FollowTable without Lower > warn:legacy.osl:10246:10246:sw/source/core/layout/tabfrm.cxx:1840: > SwTabFrame::MakeAll for master while follow is in RebuildLastLine() It's surely related to the logs above. The speculation part.. Crashes are all about timing. Hitting a 'bad spot'. Even optimized builds behave differently. Possible even a difference between master/and release builds. I tried to get a crash with a (win) debug-build too, but couldn't succeed (in the time tried). So with slower rendering no crash? Or does the optimized build take a shortcut of some kind.. Not sure if there is some trick to 'force' a crash in debug builds? Some sort ASAN approach?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>