GNOME Bugzilla – Bug 142992
Crash when exiting GnuCash
Last modified: 2018-06-29 20:43:37 UTC
I think it was a segmentation fault. GnuCash version 1.8.9. Large data file, almost 12MB, with about 9 years of data. I pressed the Save button on the main window. I waited for a couple of seconds and then I pressed the Exit button. It prompted me that my data had been changed, did I want to save it. I was surprised, because I had just saved, but I said yes. The crash occurred very shortly after that. I now suspect that the first save had not finished by the time I pressed the Exit button. The backtrace: Backtrace was generated from '/usr/bin/guile' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 1075020960 (LWP 5983)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0xffffe002 in ?? ()
+ Trace 46878
Thread 1 (Thread 1075020960 (LWP 5983))
Hmm, I thought I had fixed this a while ago, but clearly not (or it was re-introduced along the way). Yes, it's a race condition with very large data files -- if you "save" twice it gets very unhappy.
*** This bug has been marked as a duplicate of 139188 ***
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=142992. Please update any external references or bookmarks.