Problem description: Calc launches and uses a little over 65M memory. As I use the product, that gradually increases until it slows down the system. Saving my work, closing and restarting Calc resets the memory and I can work again for another 20 minutes until the system slows again and I have to cycle the app again. Steps to reproduce: 1. Launch Calc 2. Work for 10 minutes, monitor memory usage 3. .... Current behavior: Memory Leak Expected behavior: Stable memory usage. Operating System: Windows 7 Version: 3.6.4.3 release
To help to investigate, could you give extra information: - did you install any LO specific extensions? - did you undo things often? - did you notice if there was more memory leakage if you use a specific LO feature?
I don't have any specific extensions created. The spreadsheet was not imported from another app (excel, open office, etc..) I can recreate the problem from a blank spreadsheet just by entering values in cells. It does not require undo to reproduce, though I rarely use that, so no, not an issue related to undo. Unfortunately, I can not tie the memory leak to a specific feature, as I can reproduce it just by entering values in cells. Sorry I can't be of more help... Cliff On Fri, Dec 21, 2012 at 1:32 PM, <bugzilla-daemon@freedesktop.org> wrote: > Julien Nabet <serval2412@yahoo.fr> changed bug 58596<https://bugs.freedesktop.org/show_bug.cgi?id=58596> > What Removed Added CC serval2412@yahoo.fr > > *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=58596#c1> on bug > 58596 <https://bugs.freedesktop.org/show_bug.cgi?id=58596> from Julien > Nabet <serval2412@yahoo.fr> * > > To help to investigate, could you give extra information: > - did you install any LO specific extensions? > - did you undo things often? > - did you notice if there was more memory leakage if you use a specific LO > feature? > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > >
cliffa: first, thank you for your feedback. There are certainly still memory leakages but with a quite small file and just very few steps to process to trigger the leakage, it may help the investigation. So could you attach a "minimum file" where you noticed this?
One of the problem is for sure undo/redo! You can limit the number of undo steps maybe to 10 and you should have less problems. Storing the undo information is still one of our biggest memory consumers.
I have reduced the undo steps from 100 to 10 under options-memory. I will run it for a while and see if that solves the issue. Thanks, Cliff On Sat, Jan 12, 2013 at 5:14 AM, <bugzilla-daemon@freedesktop.org> wrote: > *Comment # 4 <https://bugs.freedesktop.org/show_bug.cgi?id=58596#c4> on bug > 58596 <https://bugs.freedesktop.org/show_bug.cgi?id=58596> from Markus > Mohrhard <markus.mohrhard@googlemail.com> * > > One of the problem is for sure undo/redo! > > You can limit the number of undo steps maybe to 10 and you should have less > problems. Storing the undo information is still one of our biggest memory > consumers. > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > >
Hi, (In reply to comment #5) > I have reduced the undo steps from 100 to 10 under options-memory. I will > run it for a while and see if that solves the issue. Did you noticed any improvements by changing these settings? Kind regards, Joren
Yes, that definitely resolved the performance issue. On Thu, Jan 31, 2013 at 5:27 PM, <bugzilla-daemon@freedesktop.org> wrote: > Jorendc <joren.libreoffice@telenet.be> changed bug 58596<https://bugs.freedesktop.org/show_bug.cgi?id=58596> > What Removed Added Status UNCONFIRMED NEEDINFO QA Contact > joren.libreoffice@telenet.be Ever confirmed 1 > > *Comment # 6 <https://bugs.freedesktop.org/show_bug.cgi?id=58596#c6> on bug > 58596 <https://bugs.freedesktop.org/show_bug.cgi?id=58596> from Jorendc<joren.libreoffice@telenet.be> > * > > Hi, > > (In reply to comment #5 <https://bugs.freedesktop.org/show_bug.cgi?id=58596#c5>)> I have reduced the undo steps from 100 to 10 under options-memory. I will > > run it for a while and see if that solves the issue. > > Did you noticed any improvements by changing these settings? > > Kind regards, > Joren > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > >
(In reply to comment #7) > Yes, that definitely resolved the performance issue. Ok, then we can close this bug properly :). Thanks for your feedback; Thanks Markus and Julien to look at this.