Bug 130311

Summary: calc: crash: endless loop 'saving' with 7.0.0.0
Product: LibreOffice Reporter: b. <newbie-02>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INSUFFICIENTDATA    
Severity: normal CC: suokunlong
Priority: medium    
Version: unspecified   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:

Description b. 2020-01-31 09:52:08 UTC 
Description:
not reproducible, happened three times, no relation to distinct handling found ... 

calc ver. - see below - entered into an endless loop of 4 seconds 'running ants' annonuncing 'saving document page xx of 18' or similar, 5 seconds pause with menu items still greyed out and program unresponsive, repeated with 4 seconds running ants 'saving... ' ad infinitum - big file, password protected with readonly password set, threaded and CL off, autosave on (10 or 15 minutes, not! seconds)), works better in other versions (6.2.8.2, 6.4.0.1, ~.2, ~.3), worked also with 7.0 - about 25 starts and ~ 10 hours of work, with 4 to 10 other files open parallel in the same calc ver. 

found no other way to stop it than killing with task manager, will not do further tests with that version, too many crashes, 

7.0 is missing in the select list for affected versions. 

Steps to Reproduce:
can't tell, see above

Actual Results:
endless 'saving' loop, program not accessible, 

Expected Results:
responsive program


Reproducible: Sometimes


User Profile Reset: No



Additional Info:
Version: 7.0.0.0.alpha0+ (x64)
Build ID: 07b1159b79135857dd9a450c3bb9ae0a944ebcf9
CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win; 
Locale: de-DE (de_DE); UI-Language: en-US
Calc:
Comment 1 Kevin Suo 2020-02-01 06:30:11 UTC 
(In reply to b. from comment #0)

@b.: First of all, the daily builds (i.e., 7.0.0.0.alpha0+ at this moment) are for test purpose only, it is expected that there are many many bugs including crashes in this version. For daily work, you should use a stable version (i.e., LibreOffice 6.3 at this moment).

Second, to help to investigate this crash, would you please:
1. Provide short description of the 1,2,3... steps detailing how we can reproduce this crash?
2. Provide a minimal test document with which we can use to reproduce this.

With your above description, we are not able to resolve the issue. I mark this as NEEDINFO. Once you have provided the inforation above, please set the status back to UNCONFIRMED.
Comment 2 b. 2020-02-01 14:04:03 UTC 
> @b.: First of all, the daily builds (i.e., 7.0.0.0.alpha0+ at this moment) are for test purpose only, ... 

i know, 

> 1. Provide short description of the 1,2,3... steps detailing how we can reproduce this crash?

tried to remember, no chance, 
>> not reproducible, happened three times, no relation to distinct handling found ... 

> 2. Provide a minimal test document with which we can use to reproduce this.

sheet where the problem occurred contains private data, 

> With your above description, we are not able to resolve the issue. I mark this as NEEDINFO. Once you have provided the inforation above, please set the status back to UNCONFIRMED.

>> will not do further tests with that version, 

therefore this bug report is not an approach for analysis, just a warning, or a hint if other users experience similar problems ...
Comment 3 Kevin Suo 2020-02-01 14:29:04 UTC 
(In reply to b. from comment #2)

Then let's close this as INSUFFICIENTDATA as the bug can not be fixed with the limited information so far. Let's see if other users experience the same problem with clear reproducible steps.