Bug 84364 - EDITING: Memory leak when select number of columns
Summary: EDITING: Memory leak when select number of columns
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.2.6.2 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-26 09:18 UTC by AHX2323
Modified: 2015-05-06 14:23 UTC (History)
1 user (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 AHX2323 2014-09-26 09:18:22 UTC
Problem description: 

Steps to reproduce:
3. run "htop" ("apt-get install htop")
   and see memory usage;
1. open *.xsl or *.ods document;
2. select three or more columns;
   select entire columns (not some cells).

Current behavior:
1. memory (RAM) usage increase
   from current value to 100%;
2. swap usage increase from 0% to 100%;
3. libreoffice will crash and
   allocated memory will return to system.

Expected behavior:
just select number of columns;
do not calculate sum, average, count of cells, etc.

Operating System: Linux (Other)
Version: 4.2.6.2 release
Comment 1 Julien Nabet 2014-09-26 17:18:12 UTC
On pc Debian x86-64 with LO Debian package 4.3.1.2, I don't reproduce this on a brand new (and empty I must recognize) file.

4.2.X is soon EOL (see https://wiki.documentfoundation.org/ReleasePlan#4.2_release)

Could you attach some example files? (have in mind that any attachment is automatically made public so remove private/confidential part).

You should give a try to last stable release 4.3.2 or if you're chasing memory leaks master sources (future 4.4) daily build (see  http://dev-builds.libreoffice.org/daily/master/)
Indeed, you must know that a lot of leaks are fixed version after version (you can take a look to git source repository, http://cgit.freedesktop.org/libreoffice/core/log/?qt=grep&q=leak).
Comment 2 QA Administrators 2015-04-01 14:47:22 UTC
Dear Bug Submitter,

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 INVALID
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
Comment 3 QA Administrators 2015-05-06 14:21:43 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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

-- The LibreOffice QA Team 

This INVALID Message was generated on: 2015-05-06

Warm Regards,
QA Team