Bug 132218 - Crash in: com::sun::star::uno::Sequence<signed char>::~Sequence<signed char>()
Summary: Crash in: com::sun::star::uno::Sequence<signed char>::~Sequence<signed char>()
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.2.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Crash
  Show dependency treegraph
 
Reported: 2020-04-18 13:10 UTC by gavinbstrange
Modified: 2022-02-04 03:42 UTC (History)
3 users (show)

See Also:
Crash report or crash signature: ["com::sun::star::uno::Sequence<signed char>::~Sequence<signed char>()"]


Attachments
Testcase; follow instruction to run (4.27 MB, application/vnd.oasis.opendocument.spreadsheet)
2020-04-26 20:35 UTC, gavinbstrange
Details
process explorer (90.99 KB, image/png)
2020-06-14 10:48 UTC, libre officer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gavinbstrange 2020-04-18 13:10:49 UTC
This bug was filed from the crash reporting server and is br-a45914cc-154c-4c85-beb0-0239f590dd4a.
=========================================
The file is a very large one; see stats below. The autocalculate has been turned off, due to the size. The error is that Calc crashes when the recalculate (F9) is used.
The fix is to turn off the Save AutoRecovery.
This makes me think the bug is that the "Save AutoRecovery" has too high a priory and crashes during recalculation as both actions can't proceed at the same time.
File stats;
4 sheets
Sheet 1: Raw data in 4 columns x 669600 rows, formulas in 20 columns x 669600 rows
Sheet 2: only formulas in 15 columns x 4480 rows (summarising data in sheet 1)
Sheet 3: Raw data used as setting approx 50 cells
Sheet 4: Formulas in 7 columns x 33 rows used to produce 2 graphs (further summarisation of sheet 1)
Recalculation takes 15 minutes approx.
Data is electric used and generated over the month in 4 second slots.
Comment 1 Telesto 2020-04-18 20:32:08 UTC
Can the document be shared publicly?
Comment 2 gavinbstrange 2020-04-26 20:35:08 UTC
Created attachment 159974 [details]
Testcase; follow instruction to run

To see the system crash open the file and one the "Adjusted" sheet copy the cells E116 to Y116 to cells E117 to Y648037. Making sure the autorecovery is on press F9. It takes about 5 minutes to crash; the calculations take about 20 minutes to complete.
Comment 3 Ming Hua 2020-04-26 23:00:56 UTC
(In reply to gavinbstrange from comment #2)
>
> ... open the file and one the "Adjusted" sheet copy the
> cells E116 to Y116 to cells E117 to Y648037.
What is the easy way to do this?  My usual "select and drag down" approach is taking ages.
Comment 4 gavinbstrange 2020-04-29 18:50:15 UTC
The easiest way is to 
1. select the cells E116 to Y116 and copy (cntl c).
2. select cell E117.
3. use the scroll bar to quickly move to the bottom of the sheet.
4. while pressing the shift button on the keyboard select cell Y648037.
this should highlight all the cells between.
5. paste (cntl v)

hope this is helpful.
Gavin
Comment 5 Ming Hua 2020-04-30 01:24:39 UTC
(In reply to gavinbstrange from comment #4)
> The easiest way is to 
> 1. select the cells E116 to Y116 and copy (cntl c).
> 2. select cell E117.
> 3. use the scroll bar to quickly move to the bottom of the sheet.
> 4. while pressing the shift button on the keyboard select cell Y648037.
> this should highlight all the cells between.
> 5. paste (cntl v)
Thanks, I gave it a try, but got my LO hang instead of crash.  It stuck at "Saving File..." and the green progress bar at the status bar for about 5 minutes until I forced it to quit manually.

Will try again later, with maybe fewer rows, my computer is likely less powerful than yours.
Comment 6 gavinbstrange 2020-05-02 10:35:03 UTC
Could I check that you are using version 6.4.2.2. On previous version of LibreOffice (6.3.n), LibreOffice would hang, as you have described. It is only the later version that seems to crash.
In terms of PC power, it also does it on my old Intel i5 (2 core) laptop with 8GBs of memory.
Comment 7 Ming Hua 2020-05-03 01:21:04 UTC
I *think* I've reproduced this.  My system got very slow and non-responsive (moving the mouse and the cursor won't move), eventually after like 10 minutes (I pressed Ctrl-Alt-Delete to try to get to the Resource Mannager during this), LO was gone and my system got responsive again.  But I didn't get any information about crash report even if I made sure I enabled it before started testing.

(In reply to gavinbstrange from comment #6)
> Could I check that you are using version 6.4.2.2. On previous version of
> LibreOffice (6.3.n), LibreOffice would hang, as you have described. It is
> only the later version that seems to crash.
I was using 6.4.3 last time and 6.4.4 RC1 this time.

Since I don't have a crash signature to compare with, I'm not marking this as CONFIRMED yet.
Comment 8 libre officer 2020-06-14 10:48:06 UTC
(In reply to gavinbstrange from comment #4)
> The easiest way is to 
> 1. select the cells E116 to Y116 and copy (cntl c).
> 2. select cell E117.
> 3. use the scroll bar to quickly move to the bottom of the sheet.
> 4. while pressing the shift button on the keyboard select cell Y648037.
> this should highlight all the cells between.
> 5. paste (cntl v)
> 
> hope this is helpful.
> Gavin

I did all the steps, it hangs for a long moment (~20-30 minutes), then became usable, hangs again for a long moment... Surprise! Windows crashed O_o

All I got is a screenshot of process explorer (see attachments), no crash report generated.


Version: 7.0.0.0.beta1 (x64)
Build ID: 94f789cbb33335b4a511c319542c7bdc31ff3b3c
CPU threads: 4; OS: Windows 10.0 Build 17763; UI render: Skia/Raster; VCL: win
Locale: fr-CH (fr_FR); UI: en-GB
Calc: threaded
Comment 9 libre officer 2020-06-14 10:48:58 UTC
Created attachment 161981 [details]
process explorer
Comment 10 libre officer 2020-06-14 10:51:04 UTC
(In reply to libre officer from comment #8)
> (In reply to gavinbstrange from comment #4)
> > The easiest way is to 
> > 1. select the cells E116 to Y116 and copy (cntl c).
> > 2. select cell E117.
> > 3. use the scroll bar to quickly move to the bottom of the sheet.
> > 4. while pressing the shift button on the keyboard select cell Y648037.
> > this should highlight all the cells between.
> > 5. paste (cntl v)
> > 
> > hope this is helpful.
> > Gavin
> 
> I did all the steps, it hangs for a long moment (~20-30 minutes), then
> became usable, hangs again for a long moment... Surprise! Windows crashed O_o
> 
> All I got is a screenshot of process explorer (see attachments), no crash
> report generated.
> 
> 
> Version: 7.0.0.0.beta1 (x64)
> Build ID: 94f789cbb33335b4a511c319542c7bdc31ff3b3c
> CPU threads: 4; OS: Windows 10.0 Build 17763; UI render: Skia/Raster; VCL:
> win
> Locale: fr-CH (fr_FR); UI: en-GB
> Calc: threaded


Erratum:
After clicking on save -> "hangs again for a long moment"
Comment 11 Xisco Faulí 2021-07-07 10:35:01 UTC
Hello,
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 12 QA Administrators 2022-01-04 03:29:51 UTC Comment hidden (obsolete)
Comment 13 QA Administrators 2022-02-04 03:42:05 UTC
Dear gavinbstrange,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp