Bug 96340 - LO Calc crashes when trying to make a chart out of a dozens of thousands of cells
Summary: LO Calc crashes when trying to make a chart out of a dozens of thousands of c...
Status: RESOLVED DUPLICATE of bug 85867
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.0.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-08 14:56 UTC by YSO
Modified: 2016-01-11 17:53 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Test doc (92.36 KB, application/vnd.oasis.opendocument.spreadsheet)
2015-12-08 14:56 UTC, YSO
Details
Backtrace Visual Studio Community 2015 (32.14 KB, text/plain)
2015-12-08 16:41 UTC, m_a_riosv
Details
Shot of the operation working on Linux (261.81 KB, image/png)
2015-12-09 11:03 UTC, YSO
Details
Shot of something akin to expected result (370.74 KB, image/png)
2015-12-09 13:30 UTC, YSO
Details

Note You need to log in before you can comment on or make changes to this bug.
Description YSO 2015-12-08 14:56:52 UTC
Created attachment 121141 [details]
Test doc

Data were imported from a csv and the data range ended up encompassing 73500 cells.

I wanted to make a line chart out of it but LO Calc systematically crashes upon opening the chart dialog after I have selected all the cells I need.

This works perfectly in MS Office Excel 2013.
Comment 1 m_a_riosv 2015-12-08 16:41:30 UTC
Created attachment 121142 [details]
Backtrace Visual Studio Community 2015

Reproducible
Win10x64
Version: 5.0.4.1 (x64)
Build ID: 2def61bcbb29a7a8611b833682fe1291910b11ad

Attached backtrace for:
Version: 5.2.0.0.alpha0+
Build ID: f34b4844473d08c0c264ba4453a875e32f5c326b
Threads 4; Ver: Windows 6.19; Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2015-12-01_06:36:58
Comment 2 YSO 2015-12-08 16:44:24 UTC
(In reply to YSO from comment #0)
> Created attachment 121141 [details]
> Test doc
> 
> Data were imported from a csv and the data range ended up encompassing 73500
> cells.
> 
> I wanted to make a line chart out of it but LO Calc systematically crashes
> upon opening the chart dialog after I have selected all the cells I need.
> 
> This works perfectly in MS Office Excel 2013.

Forget to report sysinfo:

OS: Microsoft Windows 8.1 Professionnel 64bits
Version: 6.3.9600 N/A version 9600
Comment 3 YSO 2015-12-09 11:03:41 UTC
Created attachment 121164 [details]
Shot of the operation working on Linux

This operation works on Linux, albeit with sub-par auto-detection of data series, broken chart graphics and horrid performance. 

Each and single operation on the resulting chart object seems to run on a single core and take 10-15 seconds to complete. Moving it freely with the mouse seems impossible.

Again, such loss in performance in MS Office Excel 2013 was not observed. 

OS: Arch Linux 64-bits
LO_version on Linux: 5.0.3.2

Hardware: Intel Core i5-3570K, NVIDIA GTX 780, 16 GB Ram
Comment 4 YSO 2015-12-09 13:30:10 UTC
Created attachment 121171 [details]
Shot of something akin to expected result

Further observations:

Performance when moving the chart improved to good experience when I selected the Java Environment to use. Previously, LO the case about using Java was ticked but no environment was explicitly selected.

However it's only when moving the chart. When working with the data (switching chart types, selecting data ranges) and the chart, everything is still extremely slow. 

One particular operation: switching chart type from simple lines to 3D curves ran for ~15 mins before the software became responsible again.

I'm aware this may be out of the scope of this bug, but I believe it's worth reporting such performance problems when competition handles this easily.
Comment 5 Krotow 2016-01-11 16:46:37 UTC
Same problem with LibreOffice 5.0.4.2/x64 Stable on Linux Mint 17.1 (x64), Windows 7 (x64) and Windows 10 (x64). Hardware is i3-2120/8GB RAM/128GB SSD/Intel HD4000. Simple line chart containing integer numbers in 2 columns + X-Axis text labels column rendering is nearly transparent under 5K rows, then gradually slower until 20K rows (20000 rows is rendered 2 minutes). More rows is practically unusable because of rendering freezing. Full data length (100139 rows) required for me, hanged Calc completely with 100% CPU usage for one core. Memory use was no more than 1,2 GB for LO process, Java and OpenGL disabling wasn't change anything. More likely it is ineffective rendering algorithm for charts series itself. Which is a most precise conclusion - I tried to create same chart with same data on same machine in MS Excel 2010 where chart rendering and updating was completed in no more than 10 seconds for all 100139 rows.
Comment 6 m_a_riosv 2016-01-11 17:39:41 UTC
I think a duplicate, please if you are not agree reopen it.

*** This bug has been marked as a duplicate of bug 85867 ***
Comment 7 Krotow 2016-01-11 17:53:21 UTC
(In reply to Krotow from comment #5)

Posted about rendering in 5.0.4.2 and immediately found response, which claimed, that chart rendering issue is fixed in 5.1. See https://bugs.documentfoundation.org/show_bug.cgi?id=70872#c6

So I'm downloaded and installed LibreOffice 5.1.0.1 (build: bcace328aabc4c8c10b56daa87da0a2ee6579b5a) for Linux/x64. Testing results for same chart with 2 data lines:

1) 100139 rows, both data columns has formula:

- ODS document - rendering 10 sec, switch to editing - 25 sec, switch back - 10 sec
- XLSX document (from Excel 2010) - rendering 25 sec, switch to editing - 45 sec

2) 100139 rows, data columns has values only:

ODS document - rendering 6 sec, switch to editing - 10 sec, switch back - 4 sec

20K rows in both cases are rendered in 2-3 seconds. Charts under 10K rows are visible immediately. Such results are already usable for everyday use. I can conclude that problem is technically solved.

One more thing - freeze on 2 seconds with grey rectangular smears over it when chart was partially closed by dialog window or another program at top of Calc window and then became fully visible. I seen bug report about this before, but don't remember it number.