GNOME Bugzilla – Bug 792763
deleting a transaction can cause a SIGSEGV
Last modified: 2018-06-30 00:03:30 UTC
When deleting a transaction, sometimes gnucash crashes with a core dump. Some details can be found in this ML thread: https://lists.gnucash.org/pipermail/gnucash-devel/2018-January/041459.html bt is also reported below. A couple of context info: - I'm using SQL backend (mysql) - The database has been migrated to 2.7.3 from 2.6.19, but works otherwise fine - It is likely (but I can't check easily) that the transactions that caused the crash have been inserted in an account that has subsequently been deleted. Maybe it is completely irrelevant, but it could have some relevance. Comment from JRalls: "Anyway, the problem is obvious from the first tow stack frames: You've deleted the transaction out from under one of the business pages (can't tell from the backtrace which one and it probably doesn't matter) and so there's no primary transaction. xaccTransCountSplits doesn't protect itself from being called with a null transaction (it should) and gnc_plugin_business_update_menus doesn't check that it got a transaction before calling it (it should), so boom." BT: Program terminated with signal SIGSEGV, Segmentation fault.
+ Trace 238356
This problem has been fixed in our software repository. The fix will go into the next unstable software release.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=792763. Please update any external references or bookmarks.