Bug 132262 - Crash swlo!SwTableBox::getRowSpan
Summary: Crash swlo!SwTableBox::getRowSpan
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.0.2 rc
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-19 19:44 UTC by Telesto
Modified: 2020-06-18 10:44 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["lcl_RecalcRow"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-04-19 19:44:36 UTC
Description:
Crash swlo!SwTableBox::getRowSpan

Steps to Reproduce:
1. Open the attached file attachment 143995 [details] (bug 119125)
2. Press CTRL+A in Cell A1 
3. CTRL+C
4. CTRL+V after the yellow marking first page
5. Wait 30 seconds
6. CTRL+Z -> Crash

Actual Results:
Crash

Expected Results:
No crash


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.0.0.0.alpha0+ (x64)
Build ID: 4475bcd83aac7e033fc5250f268eb922bd471e7b
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL
Comment 1 Telesto 2020-04-19 19:46:08 UTC
Also with
Versie: 6.4.0.2 (x86)
Build ID: 08d19fecdc7a2298d051e19cfdb7c35544855fc3
CPU-threads: 4; Besturingssysteem: Windows 6.3 Build 9600; UI-render: GL; VCL: win; 
Locale: nl-NL (nl_NL); UI-taal: nl-NL
Calc: CL

crashreport.libreoffice.org/stats/crash_details/c86e1aac-6d57-423d-a234-ff122942ba8c
Comment 2 Julien Nabet 2020-04-20 07:21:09 UTC
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()
Comment 3 Telesto 2020-04-20 09:25:47 UTC
(In reply to Julien Nabet from comment #2)
> 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?
Comment 4 Julien Nabet 2020-04-21 09:58:28 UTC
I gave a try with non debug build, only enable-symbols, I don't reproduce this.
If LO is ready before the 30s, should I still wait?
Comment 5 Xisco Faulí 2020-06-15 15:00:42 UTC
(In reply to Julien Nabet from comment #4)
> I gave a try with non debug build, only enable-symbols, I don't reproduce
> this.
> If LO is ready before the 30s, should I still wait?

@Telesto, please give feedback
Comment 6 Telesto 2020-06-16 08:49:45 UTC
Seems stable
Version: 7.1.0.0.alpha0+ (x64)
Build ID: a35c18aeff3b1d8f270db7e094850fb8ba1ab84a
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL