Bug 151461 - High CPU on Save
Summary: High CPU on Save
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.5.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Performance
  Show dependency treegraph
 
Reported: 2022-10-10 21:45 UTC by Pierre Fortin
Modified: 2025-04-03 03:11 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre Fortin 2022-10-10 21:45:40 UTC
Linux-rpm_deb-x86_64@tb87-TDF (rpm) 	2022-10-10 08:56:40

Goal:  Split .tsv file into 100 tabs.

Loaded a sheet with 8,679,477 rows of 9 columns.  Column 1 contains numbers from 1 to 100.  Turned on auto-filter, selected rows containing "1", copied/pasted[1] into a new sheet(tab) named "1". Repeated for "2".  

Try to save as .ods, it appears to save -- progress bar suddenly stops moving and CPU climbs to nearly 800% without saving anything.

zip file (132139669; expands to 453287225) is at:
https://drive.google.com/file/d/1-A5Ks3NjwVh1IMveaVhbwemb-dMwyD6C/view?usp=sharing

[1] Select "1", Ctrl+*, Ctrl+c, new tab & rename it, Ctrl+v.
    Want to repeat 99 more time for 2-100...

Operating System: Mageia 9
KDE Plasma Version: 5.25.90
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 6.0.0-server-2.mga9 (64-bit)
Graphics Platform: X11
Processors: 20 × 12th Gen Intel® Core™ i7-12700K
Memory: 125.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT
Manufacturer: Dell Inc.
Product Name: XPS 8950
Comment 1 m_a_riosv 2022-10-11 00:19:40 UTC
Reproducible, after a while LO crash, recover the file, but no crash report.
Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: a7683a16e98def4198e1f74a93fecdaacbf639e7
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo
Comment 2 QA Administrators 2025-04-03 03:11:12 UTC
Dear Pierre Fortin,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug