GNOME Bugzilla – Bug 760561
Memory leak in reports
Last modified: 2018-06-29 23:46:21 UTC
I noticed memory leak in gnucash 2.6.10 and 2.6.11 for Windows. To reproduce bug I open any report and close it multiple times. Each time I open new tab consumed memory is increased by 15-20 Mb, and after closing tab memory is not decreased. This can lead up to 700 Mb after several steps. The problem can be reproduced on empty database with common accounts. I would appreciate if someone fix this bug.
I checked several 2.6 versions. 2.6.4 works fine without memory leak. Versions starting from 2.6.5 have memory leak. Seems there is a regression in 2.6.5.
Thanks for narrowing down the source of the memory leak. Unfortunately the resulting set of changes is still very wide and I'm having trouble identifying potential commits that could introduce this. Would you be willing to narrow this further by testing the nightly builds between 2.6.4 and 2.6.5 ? They can be found here: http://code.gnucash.org/builds/win32/maint/ There are 31 nightly builds. That should take approximately 5 download and install actions (if you start with the one in the middle and cut the remaining half in half again afterwards and so on). Thanks.
Thank you for your response! I checked night builds with binary search algorithm you mentioned: gnucash-2.6.4-2014-10-27-git-5acdbb6+-setup.exe - without bug gnucash-2.6.4-2014-11-09-git-766bb51+-setup.exe - unable to run gnucash-2.6.4-2014-11-10-git-766bb51+-setup.exe - with bug Some builds can not be installed or doesn't work because of wrong DLLs included in setup bundle. Seems regression is within these builds. Another point is that in 2014-11-10 build I see changed external libraries: libjpeg-7.dll -> libjpeg-9.dll libgcrypt-11.dll -> libgcrypt-20.dll etc Seems external libraries were upgraded. May be memory leak is caused by this versions upgrade.
(In reply to Dmitry from comment #3) > Another point is that in 2014-11-10 build I see changed external libraries: > libjpeg-7.dll -> libjpeg-9.dll > libgcrypt-11.dll -> libgcrypt-20.dll > etc > Seems external libraries were upgraded. > May be memory leak is caused by this versions upgrade. Thank you for the binary search. It confirms my worry. Between the two dates you mention we have upgraded webkitgtk in the windows build. That's the only change I find that could possibly lead to a memory leak. I'm afraid there isn't much I can do about this right now. I'll keep the bug open though in the hopes someone else can look into it or I get to it myself somewhere in the future.
GnuCash bug tracking has moved to a new Bugzilla host. The new URL for this bug is https://bugs.gnucash.org/show_bug.cgi?id=760561. Please continue processing the bug there and please update any external references or bookmarks.