Remember that you can get automatic save on each transaction by switching to the Sqlite3 backend by using File>Save As... and selecting Sqlite3 from the drop-down at the top of the dialog box. Note that Sqlite3 changes the file in place so there are no GnuCash backups. Set up File History or some other automatic backup program instead.
That's not to suggest that you shouldn't figure out as much as you can about the cause of the crashes and then file a bug report. The absolute best information is a stack trace, but that can be a bit challenging on Windows. See https://wiki.gnucash.org/wiki/Stack_Trace#Windows for instructions. Regards, John Ralls > On Jul 21, 2022, at 8:47 AM, A Harvey <gah1...@gmail.com> wrote: > > I have a similar problem. It occurs in both 4.10.x and 4.11. I think it > also occurred in 4.9 but can't remember. I encountered it on windows 10 > and windows 11. I run Gnucash monthly. Importing CSV bank and credit card > statements always works. I don't import investment transactions as > massaging the data to import as a CSV would be more work than just entering > them directly. Typically, I either start typing a transaction and then > accept the suggested description and transfer account, or I duplicate an > existing transaction and modify the amounts. Most of the transactions are > automatic dividend/interest reinvestments for stock/bond funds. > Here is the problem. I will enter several investment transactions, then > type ctl-s or click the save button. Sometimes Gnucash exits without > saving and without deleting the lock file. This will happen roughly 3 > times over the course of entering 25 or so transactions. Some subset of > unsaved transactions are lost. I've developed the habit of saving after > each transaction so that I never have more than one unsaved transaction > when it crashes. I haven't been able to detect any pattern with respect to > which accounts, what types of transaction or other factors may be > involved. Restarting Gnucash and reentering the lost transaction exactly > as before works fine. > > I will enable the logging (-debug and -extra? I'll read the Wiki on how to > turn that stuff on) and check the trace file next time I run Gnucash to see > whether it captures anything useful when and if it crashes again. > > Regards, > -Arthur > > On Wed, Jul 20, 2022 at 2:16 AM David T. via gnucash-user < > gnucash-user@gnucash.org> wrote: > >> I apologize if my response seemed testy. It's extremely frustrating to be >> working on a large data set with lots of complex transactions ("How exactly >> should the capital gains for a stock position with multiple purchase lots >> and an intervening split be tracked?"), finally work out how those complex >> transactions get recorded, enter them, go to save the result, only to have >> the program crash out. >> >> I will certainly try closing at least the one report I have open, as your >> idea that the report derives information from that reconciled account seems >> a reasonable possibility. >> >> >> >> On July 20, 2022 12:42:42 AM GMT+03:00, Adrien Monteleone < >> adrien.montele...@lusfiber.net> wrote: >>> I wasn't trying to cause you work, just offering ideas on tracking down >> the cause. Eliminating variables is part of that process. Lots of tabs and >> especially reports open = variables. >>> >>> I'm going to hazard there is a report that feeds off one of those >> registers (likely the one you are reconciling) that is a good candidate, >> thus closing everything but that register should reveal if that is the case. >>> >>> But perhaps an upgrade to 4.11 would suit you better. You'll end up there >> most likely anyway. >>> >>> Regards, >>> Adrien >>> >>> On 7/19/22 1:41 PM, David T. via gnucash-user wrote: >>>> Adrien, >>>> >>>> Thanks for the suggestions. >>>> >>>> It would seem to me that Finish/Ctrl-S is pretty reduced. >>>> >>>> I currently have about 12 tabs open. 10 registers, the CoA, and one >> report (granted, it's a multicolumn report). >>>> >>>> Saving after every edit is a remarkably annoying idea, especially given >> how long each save takes. I won't be doing that. >>>> >>>> As for a backup, I'm not sure why I'd go to a backup. The problem >> doesn't always happen, so I don't believe it's a problem with data >> corruption. I'm trying to move forward with my books, not backward. >>>> >>>> Nothing is holding me back from 4.11. >>> >>> >>> _______________________________________________ >>> gnucash-user mailing list >>> gnucash-user@gnucash.org >>> To update your subscription preferences or to unsubscribe: >>> https://lists.gnucash.org/mailman/listinfo/gnucash-user >>> If you are using Nabble or Gmane, please see >> https://wiki.gnucash.org/wiki/Mailing_Lists for more information. >>> ----- >>> Please remember to CC this list on all your replies. >>> You can do this by using Reply-To-List or Reply-All. >> _______________________________________________ >> gnucash-user mailing list >> gnucash-user@gnucash.org >> To update your subscription preferences or to unsubscribe: >> https://lists.gnucash.org/mailman/listinfo/gnucash-user >> If you are using Nabble or Gmane, please see >> https://wiki.gnucash.org/wiki/Mailing_Lists for more information. >> ----- >> Please remember to CC this list on all your replies. >> You can do this by using Reply-To-List or Reply-All. >> > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
