GNOME Bugzilla – Bug 166840
crash with MALLOC_CHECK_=2
Last modified: 2018-06-29 20:49:51 UTC
Version details: 1.8.11 Distribution/Version: Fedora Core Development tree Originally reported by Tim Waugh at: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=72823 ... Description of Problem: I saw gnucash crash, when MALLOC_CHECK_ was set to 2. This means that there is some dodgy memory handling going on of some sort. Version-Release number of selected component (if applicable): gnucash-1.6.6-7 How Reproducible: Seems to be consistent. Here's one way of getting it to crash that I've found: 1. Set MALLOC_CHECK_=2 2. In a register window, tab over to the withdrawal column. 3. Type '1', then backspace. 4. Shift-tab. ... It persists on 1.8.11. Here's the backtrace: Here's the backtrace: Program received signal SIGABRT, Aborted.
+ Trace 55518
Thread NaN (LWP 29484)
This backtrace seems somewhat weird. For example, frame #5 seems to imply that g_free() is being called with a NULL value, but in that case it shouldn't be calling free(). So this backtrace clearly isn't showing what's going on. I'm not at all surprised that there are memory issues with GnuCash -- there are certainly errors in Guile ;) That notwithstanding, if someone wants to submit a patch to correct this I'll gladly apply it. Otherwise, I think I'll wait until the g2 port and see if we can get that to run mostly-clean under valgrind.
Is this still existing in SVN, the upcoming 1.9/2.0? That branch has been checked by valgrind several times now, so this is likely to be fixed.
Still happens. Here's the backtrace from svn12369 (it's what I have ATM built.)
+ Trace 65335
With backtrace and clear steps for reproduction, this was easy to fix. Thanks for the good report. Fixed in svn 13243.
Marking the version where this has been fixed.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=166840. Please update any external references or bookmarks.