Bug 120441 - FILEOPEN: LibO consumes all memory on my Debian when loading this .XLS file
Summary: FILEOPEN: LibO consumes all memory on my Debian when loading this .XLS file
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.1.2.1 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks: Memory
  Show dependency treegraph
 
Reported: 2018-10-09 09:11 UTC by Raphaël Hertzog
Modified: 2019-07-20 13:35 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
XLSX file leading to the problem (14.00 KB, application/vnd.ms-excel)
2018-10-09 09:12 UTC, Raphaël Hertzog
Details
callgrind trace (842.11 KB, text/plain)
2018-11-22 11:55 UTC, Raphaël Hertzog
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Raphaël Hertzog 2018-10-09 09:11:49 UTC
Description:
When I open this document, LibreOffice 6.1.2-1 (from Debian Testing/Unstable) quickly starts to consume all memory to the point that the the computer becomes unresponsive in a few minutes. (If I wait long enough, the Linux OOM killer might end up killing the application.)

Steps to Reproduce:
1. Open the attached file.
2. Wait.


Actual Results:
LibreOffice Calc started to consume more and more memory until the computer became unresponsive to any input.

Expected Results:
I should be able to look at the document without LibreOffice rendering my computer unresponsive due to continuous use of RAM.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 6.1.2.1
Build ID: 1:6.1.2-1
Threads CPU : 4; OS : Linux 4.18; UI Render : by default; VCL: gtk3; 
Locale : fr-FR (fr_FR.UTF-8); Calc: group threaded
Comment 1 Raphaël Hertzog 2018-10-09 09:12:41 UTC
Created attachment 145508 [details]
XLSX file leading to the problem

This is the problematic XLSX file.
Comment 2 Xisco Faulí 2018-10-09 11:37:44 UTC
I can't reproduce it in

Version: 6.2.0.0.alpha0+
Build ID: 98cc91efd7862d39b3c33b85b744721bec935938
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: threaded

nor in

Versió: 6.1.2.1
ID de la construcció: 1:6.1.2~rc1-0ubuntu0.16.04.1
Fils de CPU: 4; SO: Linux 4.15; Renderitzador de la IU: per defecte; VCL: gtk3; 
Configuració local: ca-ES (ca_ES.UTF-8); Calc: group threaded

To be certain the reported issue is not
related to corruption in the user profile, could you please reset your
Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and
re-test?

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present
Comment 3 Raphaël Hertzog 2018-10-09 12:29:39 UTC
I started libreoffice in safe mode and opened the file and I had the same problem.
Comment 4 raal 2018-10-09 19:27:33 UTC
I can not confirm with Version: 6.2.0.0.alpha0+
Build ID: e9c1cbce903d325b1e19602d72765511589f5bf2
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3;
Comment 5 Xisco Faulí 2018-11-09 13:42:29 UTC
Does it work if you disable OpenGl ? -> https://wiki.documentfoundation.org/OpenGL

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present
Comment 6 Raphaël Hertzog 2018-11-09 14:47:06 UTC
I disabled OpenGL (disabled the checkbox "Utiliser l'accélération matérielle" in my French Libreoffice) and the issue was still present. FWIW the document doesn't contain any picture.

Since my initial report I have upgraded to version 6.1.3~rc1-2 of the Debian package (from Debian unstable) but the issue persists. I tried to run it in different locales (LC_ALL=C.UTF-8 or LC_ALL=C) but the problem was also present.
Comment 7 Joel Madero 2018-11-20 11:39:59 UTC
Version: 6.2.0.0.alpha1+
Build ID: 1647bc1309dcd313dff2614f4844b71b1c558dee
CPU threads: 2; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: threaded

Linux Mint 19

No problem at all.

Because this seems to be specific to your environment, we may need you to do some more of the leg work to confirm the issue and get us information on the cause. When you have time please jump into our Quality Assurance chat and ask the room for guidance on how to create necessary logs.

https://irc.documentfoundation.org/?settings=#libreoffice-qa
Comment 8 Raphaël Hertzog 2018-11-22 11:55:35 UTC
Created attachment 146904 [details]
callgrind trace

Please find attached a callgrind log where callgrind was only active after libreoffice started during the time at which the memory use was growing without limit.

I had a quick look with kcachegrind and there's a "FindFocus" funtion which seems to be called way too much. It comes from libvclplug_gtk3lo.so so the issue is likely specific to the GTK-3 version of LibreOffice.
Comment 10 tommy27 2018-12-07 05:52:39 UTC
try 6.1.3
Comment 11 Raphaël Hertzog 2018-12-07 09:18:18 UTC
I tried with version 6.1.3-2 from Debian Unstable and I still have the problem. I also tried with 6.3.0.0.alpha0 from https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@86-TDF/current/ (dated December 1st) and I can also reproduce the problem.
Comment 12 Raphaël Hertzog 2018-12-07 09:30:41 UTC
Note that the file must be writable when you open it with LibreOffice to be able to reproduce the problem. If you open it in read-only mode, then it works fine.
Comment 13 Oliver Grimm 2019-07-09 09:16:33 UTC
CANNOT confirm here 

Version: 6.1.5.2
Build-ID: 1:6.1.5-3
CPU-Threads: 2; BS: Linux 4.19; UI-Render: Standard; VCL: gtk3; 
Gebietsschema: de-DE (de_DE.utf8); Calc: group threaded; Debian stable
Comment 14 Xisco Faulí 2019-07-09 09:26:18 UTC
Hello Raphaël,
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 15 Raphaël Hertzog 2019-07-20 13:26:42 UTC
Hello,

I can no longer reproduce the problem with version 1:6.3.0~rc1-1 currently in Debian unstable. From my point of view, it's gone so I close the bug. It might also be an update somewhere else in the GTK stack that fixed the issue, I have no idea.