Bug 132506 - Memory leaking when pressing Ignore Once/ Correct All multiple times
Summary: Memory leaking when pressing Ignore Once/ Correct All multiple times
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.0.0.alpha0+
Hardware: All All
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Memory
  Show dependency treegraph
 
Reported: 2020-04-28 20:49 UTC by Telesto
Modified: 2024-09-07 03:18 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Valgrind trace (15.86 KB, application/x-bzip)
2020-04-29 20:33 UTC, Julien Nabet
Details
Valgrind trace (1.11 MB, application/x-bzip)
2020-04-29 20:58 UTC, Julien Nabet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-04-28 20:49:44 UTC
Description:
Memory leaking when pressing Ignore Once multiple times

Steps to Reproduce:
1. Open attachment 160044 [details] 
2. Monitor memory usage development (Process monitor)
2. Open the Spell Checker (F7) Any dictionary except latin will do
3. Press and hold ALT+I (Ignore Once)for a while (40 seconds?)
4. Close without save
5. Reopen the file (notice the memory bump)
6. Repeat.. 2-5

Note same happens with 'Ignore All' but the ignoring supposed to work a full session, so not sure if it's leaking.. I guess so, but...

Actual Results:
Memory usage builds up

Expected Results:
Memory should be released


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.0.0.0.alpha0+ (x64)
Build ID: f924658e45f256544e43c3fdb2af9b585d0f0933
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL
Comment 1 Telesto 2020-04-28 20:51:12 UTC
@Julien 
Reproducible on Linux? Valgrind trace?
Comment 2 Julien Nabet 2020-04-29 20:33:44 UTC
Created attachment 160092 [details]
Valgrind trace

It seems we should use --leak-check=full but don't know how to add it so I think the trace is useless.
Comment 3 Telesto 2020-04-29 20:54:45 UTC
Not in 4.4.7.2
Comment 4 Julien Nabet 2020-04-29 20:58:13 UTC
Created attachment 160093 [details]
Valgrind trace

I found the way to enable leak-check=full with:
export VALGRIND_OPTS="--memcheck:leak-check=yes"
Comment 5 Buovjaga 2020-08-25 11:41:40 UTC
(In reply to Telesto from comment #3)
> Not in 4.4.7.2

Are you sure? With this version, I did notice a 5-6M difference after reopening.
Comment 6 Telesto 2020-08-25 11:52:57 UTC
(In reply to Buovjaga from comment #5)
> (In reply to Telesto from comment #3)
> > Not in 4.4.7.2
> 
> Are you sure? With this version, I did notice a 5-6M difference after
> reopening.

A) Long while back; no recollection of me even reporting this ..
B) Have to check a Linux x64 build. As these builds do expose the problem more obviously. Comparing x32 with x64 builds is like comparing Apples with Oranges (in certain way)
Comment 7 QA Administrators 2022-09-07 03:58:42 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2024-09-07 03:18:29 UTC
Dear Telesto,

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