Bug 126467 - Memory leak, crushes OS
Summary: Memory leak, crushes OS
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.0.7.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-18 19:45 UTC by radim.janos
Modified: 2020-01-19 20:25 UTC (History)
2 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 radim.janos 2019-07-18 19:45:27 UTC
Description:
When you try to open a recently opened file (the dropdown arrow from the FILEOPEN icon), from an empty calc spreadsheet, the program freezes and within the next few seconds fills up your whole RAM, everything, until your pc is unusable and you have to restart the pc.

Steps to Reproduce:
1. Open Calc. You are in a an empty spreadsheet.
2. Click the dropdown arrow next to the file-open icon.
3. Watch your memory get filled up and your pc get unusable if you don't manage to quickly kill the process.

I reproduced this on both my personal and my company pc (after a fresh install of linux mint).

Actual Results:
LO freezes and your memory gets filled up, freezing your pc when it is full.

Expected Results:
At least for the program to crash and not jeopardizing all unsaved data on the pc.
Ideally the recently opened file should just load. Either next to the unsaved new doc, but it can be assumed that the empty spreadsheet can be discarded if empty.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Comment 1 Xisco Faulí 2019-07-18 20:11:10 UTC
Thank you for reporting the bug.
it seems you're using an old version of LibreOffice.
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 2 radim.janos 2019-07-20 12:36:22 UTC
Hello Xisco Faulí,
thank you for the quick reply. I didn't want to upgrade my base latest linux-mint libreoffice version, but after installing now the new 6.2.5, I am happy to say that this bug is not there anymore.
Thank you.

ps: Although I am still sad that the 6.0.7 is still the default libre-office version even in the new linux-mint 19.2. I'm afraid that many people could face this issue.
Comment 3 QA Administrators 2019-07-21 02:47:59 UTC Comment hidden (obsolete)
Comment 4 raal 2019-07-21 05:57:40 UTC
I doesn't see this bug in Version: 6.4.0.0.alpha0+
Build ID: 47a774fbef8c224e4853de3fdd0230b9442bb716
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 

You can use appimage or snap for testing>
https://www.libreoffice.org/download/appimage/
https://www.libreoffice.org/download/snap/
Comment 5 QA Administrators 2020-01-18 03:34:52 UTC
Dear radim.janos,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
 
Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-NeedInfo-Ping