PS I’ve saved before-and-after copies of the relevant gnucash files as BookA.gnucash and BookB.gnucash.
BookA performs without crashing with the adjusted date-range, BookB causes a corrupt report, including many irrelevant transactions. The difference between BookA (before) and BookB (after) the changes I made today is in a 10-split transaction. The Club (not the Charity) was to have had a Christmas Meal last week, and ten members had paid for it in advance. In the event, Covid caused this to be cancelled, and 10 members opted not to have a refund, but to transfer the price of the meal to the Charity account. I made a transfer for ten meals from the Club’s bank account to the Charity’s, and recorded this as a single transaction with a split to account for each member’s contribution, identifying each donor in the memo field of the split. As a workaround, I expect I can split the single deposit from the Club’s bank account into the Charity’s as ten individual transactions, and experiment with various combined deposits into BookA. Michael > On 19 Dec 2021, at 08:06, Michael Hendry <hendry.mich...@gmail.com> wrote: > > Here is the most recent crash report following a change to the date range of > a saved report: > > Process: Gnucash [13484] > Path: /Applications/Gnucash.app/Contents/MacOS/Gnucash > Identifier: org.gnucash.Gnucash > Version: 4.4-1 (4.4-1) > Code Type: X86-64 (Native) > Parent Process: ??? [1] > Responsible: Gnucash [13484] > User ID: 501 > > Date/Time: 2021-12-19 07:45:03.169 +0000 > OS Version: macOS 11.6.1 (20G224) > Report Version: 12 > Bridge OS Version: 6.0 (19P549) > Anonymous UUID: F889FA2B-0F71-CD50-6275-EA85633D47E5 > > Sleep/Wake UUID: 3581F509-93A8-4ECD-B111-010BC4BF36B3 > > Time Awake Since Boot: 27000 seconds > Time Since Wake: 2500 seconds > > System Integrity Protection: enabled > > Crashed Thread: 0 Dispatch queue: com.apple.main-thread > > Exception Type: EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: EXC_I386_GPFLT > Exception Note: EXC_CORPSE_NOTIFY > > Termination Signal: Segmentation fault: 11 > Termination Reason: Namespace SIGNAL, Code 0xb > Terminating Process: exc handler [13484] > > Thread 0 Crashed:: Dispatch queue: com.apple.main-thread > 0 libgnc-gnome-utils.dylib 0x000000010eda7bdf gnc_set_busy_cursor > + 111 > 1 libgnc-gnome-utils.dylib 0x000000010ee40f1a > _wrap_gnc_set_busy_cursor + 58 > 2 libguile-2.2.1.dylib 0x000000010e82d53d vm_regular_engine + > 1501 > 3 libguile-2.2.1.dylib 0x000000010e82c0b3 scm_call_n + 723 > 4 libguile-2.2.1.dylib 0x000000010e7a6090 scm_call_3 + 48 > 5 libguile-2.2.1.dylib 0x000000010e82d53d vm_regular_engine + > 1501 > 6 libguile-2.2.1.dylib 0x000000010e82c0b3 scm_call_n + 723 > 7 libguile-2.2.1.dylib 0x000000010e7a600a scm_call_1 + 26 > … > > > I keep records of donations made to my Rotary Club’s charitable trust by > individual members so that I can claim Gift Aid on these gifts, and this > worked perfectly at the time the last claim fell due at the beginning of > April this year (the Club’s accounts run from July to June). > > I’ve recorded a batch of recent relevant transactions, and ran the report for > April 2020 to March 2021 before changing the date range to 1 Apr 2021 to 31 > Mar 2022 and the Report Name to “Gift Aid Report for 2021-2022” and clicking > “Apply”. > > Usually this results in a crash, but sometimes a faulty report is produced, > including some accounts which are not in the selection made and missing some > which should be included. > > I’d appreciate advice on the best way to investigate and report further on > this issue. > > Regards, > > Michael > _______________________________________________ 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.
