Bug 127957 - calc using scenarios crash after 5 minutes away
Summary: calc using scenarios crash after 5 minutes away
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.3.2.2 release
Hardware: All All
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Crash
  Show dependency treegraph
 
Reported: 2019-10-04 01:30 UTC by ted bug
Modified: 2021-08-18 16:35 UTC (History)
3 users (show)

See Also:
Crash report or crash signature: [sal3.dll]


Attachments
macos crashlog after force quit (1.33 MB, text/plain)
2019-10-04 01:34 UTC, ted bug
Details
sample file to reproduce crash (8.18 KB, application/vnd.oasis.opendocument.spreadsheet)
2019-10-04 06:22 UTC, ted bug
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ted bug 2019-10-04 01:30:55 UTC
Description:
simple scenarios in calc will crash at save after switching windows to different apps for around 5 minutes idle.
macos crash log included.
steps below is to emulate normal working condition that caused the crash everytime . i was able to reproduce it all the time after writing down each steps to narrow down the cause.

Steps to Reproduce:
1.create 2 columns and a few rows of data from a1 to b5
2. highlight a2 to b5 and create scenario 1, display border no, prevent change no
3. create scenario 2 for the same data
4. enter random data just to differentiate
5. open navigator and click a/b button
6. double click to change to scenario 1
7. again change to sceneario 2
8. delete scenario 2
9. change to scenario 1
10. create scenario 2 again like step 3
11. change to scenario 1, start a timer using your phone or just make note of the time
12. switch app and work on something else for at least 5 minutes
13. come back to calc
14. click here and there to change focus to a1
15. click save

Actual Results:
it will crash, with a receovery dialog open, but clicking ok will just hang.

Expected Results:
save the document normally.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
saving the document before switching app is fine and won't crash. but people forget and work on other stuff

Version: 6.3.2.2
Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c
CPU threads: 4; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; 
Locale: en-AU (en_AU.UTF-8); UI-Language: en-GB
Calc: threaded
Comment 1 ted bug 2019-10-04 01:34:05 UTC
Created attachment 154744 [details]
macos crashlog after force quit
Comment 2 ted bug 2019-10-04 06:22:47 UTC
Created attachment 154745 [details]
sample file to reproduce crash
Comment 3 Oliver Brinzing 2019-10-05 16:44:08 UTC
reproducible with:

Version: 6.3.2.2 (x64)
Build-ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; 
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
Calc: 

btw: LO crashed at:
> 14. click here and there to change focus to a1
Comment 4 Oliver Brinzing 2019-10-05 16:58:37 UTC
with 

Version: 6.4.0.0.alpha0+ (x64)
Build ID: b0b8851021cee26412182b51ed28fe574632a4d6
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: de-DE (de_DE); UI-Language: en-US
Calc: threaded

LO crashed at:
> 15. click save

warn:vcl.schedule:2636:3028:vcl/source/app/scheduler.cxx:373: we're too early - restart the timer (6ms)!
warn:vcl.schedule:2636:3028:vcl/source/app/scheduler.cxx:373: we're too early - restart the timer (10ms)!
warn:sfx.control:2636:3028:sfx2/source/control/dispatch.cxx:1309: Childwindow slot missing: 25917
warn:sfx.control:2636:3028:sfx2/source/control/dispatch.cxx:1309: Childwindow slot missing: 25917
warn:vcl.schedule:2636:3028:vcl/source/app/scheduler.cxx:373: we're too early - restart the timer (4ms)!
warn:xmloff:2636:3028:xmloff/source/style/impastpl.cxx:395: Adding duplicate family table-column with mismatching mapper ! class SvXMLExportPropertyMapper * __ptr64 class SvXMLExportPropertyMapper
warn:xmloff:2636:3028:xmloff/source/style/impastpl.cxx:395: Adding duplicate family table-row with mismatching mapper ! class SvXMLExportPropertyMapper * __ptr64 class SvXMLExportPropertyMapper
warn:xmloff:2636:3028:xmloff/source/style/impastpl.cxx:395: Adding duplicate family table-cell with mismatching mapper ! class SvXMLExportPropertyMapper * __ptr64 class XMLShapeExportPropertyMapper
warn:editeng:2636:3028:editeng/source/uno/unofield.cxx:404: Id service unknown: 5
warn:editeng:2636:3028:editeng/source/uno/unofield.cxx:404: Id service unknown: 2
warn:editeng:2636:3028:editeng/source/uno/unofield.cxx:404: Id service unknown: 5
warn:editeng:2636:3028:editeng/source/uno/unofield.cxx:404: Id service unknown: 10
warn:editeng:2636:3028:editeng/source/uno/unofield.cxx:404: Id service unknown: 2
warn:editeng:2636:3028:editeng/source/uno/unofield.cxx:404: Id service unknown: 3
warn:editeng:2636:3028:editeng/source/uno/unofield.cxx:404: Id service unknown: 5
warn:editeng:2636:3028:editeng/source/uno/unofield.cxx:404: Id service unknown: 2
warn:editeng:2636:3028:editeng/source/uno/unofield.cxx:404: Id service unknown: 5
warn:editeng:2636:3028:editeng/source/uno/unofield.cxx:404: Id service unknown: 10
warn:editeng:2636:3028:editeng/source/uno/unofield.cxx:404: Id service unknown: 2
warn:editeng:2636:3028:editeng/source/uno/unofield.cxx:404: Id service unknown: 3
warn:xmloff:2636:3028:xmloff/source/style/impastpl.cxx:395: Adding duplicate family table-column with mismatching mapper ! class SvXMLExportPropertyMapper * __ptr64 class SvXMLExportPropertyMapper
warn:xmloff:2636:3028:xmloff/source/style/impastpl.cxx:395: Adding duplicate family table-row with mismatching mapper ! class SvXMLExportPropertyMapper * __ptr64 class SvXMLExportPropertyMapper
warn:xmloff:2636:3028:xmloff/source/style/impastpl.cxx:395: Adding duplicate family table-cell with mismatching mapper ! class SvXMLExportPropertyMapper * __ptr64 class XMLShapeExportPropertyMapper
Assertion failed: nPrevIndex >= 0 && "coverity#1438402", file D:/sources/libo-core/sc/source/filter/xml/xmlexprt.cxx, line 862
Comment 5 Telesto 2020-05-06 18:29:08 UTC
crashreport.libreoffice.org/stats/crash_details/e1a77c28-0559-47f4-944b-935b04493501
Comment 6 Telesto 2020-05-06 19:04:12 UTC
How do I use the example file: bug 154745 
I got a crash, once.. so certainly something but not sure what I did
Comment 7 Xisco Faulí 2020-05-14 08:58:27 UTC
This issue is blocked by bug 133028 at the moment
Comment 8 Justin L 2021-08-18 16:35:33 UTC
1.) open Untitled 2.ods
2.) select A2 - B5
3.) Tools - Scenarios.  Display borders (no), prevent changes (no)
4.) tools - scenarios. Set name to num2. No borders, No prevent change
5.) make some random changes in the data.
6.) Delete Num2 scenario and select earlier scenario
7.) tools - scenarios. Set name to num2. No borders, No prevent change
8.) View - Navigator - Scenarios - Switched to earlier scenario
9.) 11:19 - documented these steps in firefox and checked my email.
10.) 11:25 - select cell A1 and hit save.

Crash seen in bibisect 6.4. No crash in bibisect 6.2 or 7.3 master.
It SEEMS to have been fixed in 7.0. I tried bibisecting it, but it is hard to be confident that these steps have been followed accurately. Plus, the brain doesn't handle the fact that in this "fixed" case, a crash is marked as bisect good, and a successful save is marked as bisect bad. Sometimes it took 3 attempts to get a crash.

In any case, I tried 4 times on master and didn't get a crash. So I'll mark as WORKSFORME.