Thanks, John.
Here's the thread 0 (the crashed thread) stack trace, machine registers
and instruction stream from the crash report. I think that's probably
everything relevant in the report.
Cheers,
Peter
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libgnc-engine.dylib 0x00000001020079ad
qof_instance_get_destroying + 77
1 libgnc-engine.dylib 0x0000000101f53c8b
xaccSplitDestroy + 43
2 libgnc-engine.dylib 0x0000000101f5966c do_destroy + 300
3 libgnc-engine.dylib 0x0000000102009030
qof_commit_edit_part2 + 272
4 libgnc-engine.dylib 0x0000000101f56e43
xaccTransCommitEdit + 339
5 libglib-2.0.0.dylib 0x0000000100561d2d g_list_foreach + 45
6 libgnc-engine.dylib 0x0000000102006231
qof_collection_foreach + 161
7 libgnc-engine.dylib 0x000000010201019a
qof_object_book_end + 138
8 libgnc-engine.dylib 0x0000000101ffec21
qof_book_destroy + 145
9 libgnc-engine.dylib 0x0000000102017bc6
QofSessionImpl::~QofSessionImpl() + 150
10 libgnc-engine.dylib 0x0000000102017ea3
qof_session_destroy + 19
11 libgnc-engine.dylib 0x0000000101fd751f
gnc_clear_current_session + 31
12 libgnc-gnome-utils.dylib 0x00000001009bf29c gnc_file_quit + 76
13 libgnc-engine.dylib 0x0000000101fbf322 call_hook + 114
14 libglib-2.0.0.dylib 0x0000000100556fed
g_hook_list_marshal + 125
15 libgnc-engine.dylib 0x0000000101fbf222 gnc_hook_run + 146
16 libgnc-gnome-utils.dylib 0x00000001009c3b2b gnc_shutdown + 59
17 libgnc-gnome-utils.dylib 0x00000001009cd69d
gnc_main_window_timed_quit + 29
18 libglib-2.0.0.dylib 0x0000000100562be4
g_timeout_dispatch + 20
19 libglib-2.0.0.dylib 0x0000000100566cec
g_main_context_dispatch + 348
20 libglib-2.0.0.dylib 0x000000010056705d
g_main_context_iterate + 525
21 libglib-2.0.0.dylib 0x000000010056737a g_main_loop_run
+ 218
22 libgtk-3.0.dylib 0x0000000100c3b11a gtk_main + 74
23 libgnc-gnome-utils.dylib 0x00000001009c36fc
gnc_ui_start_event_loop + 76
24 org.gnucash.Gnucash 0x0000000100160a86
scm_run_gnucash(void*, int, char**) + 1078
25 libguile-2.2.1.dylib 0x0000000100398932
invoke_main_func + 34
26 libguile-2.2.1.dylib 0x0000000100377b3f c_body + 15
27 libguile-2.2.1.dylib 0x000000010040534b
vm_regular_engine + 1467
28 libguile-2.2.1.dylib 0x0000000100403ef5 scm_call_n + 773
29 libguile-2.2.1.dylib 0x0000000100400922 catch + 498
30 libguile-2.2.1.dylib 0x0000000100377b09
scm_c_with_continuation_barrier + 137
31 libguile-2.2.1.dylib 0x000000010040048f with_guile + 63
32 libgc.1.dylib 0x00000001004d4ef6
GC_call_with_stack_base + 22
33 libguile-2.2.1.dylib 0x00000001003fe4ab scm_with_guile + 43
34 libguile-2.2.1.dylib 0x00000001003988f5 scm_boot_guile + 69
35 org.gnucash.Gnucash 0x00000001001605f9
Gnucash::Gnucash::start(int, char**) + 617
36 org.gnucash.Gnucash 0x0000000100161191 main + 1009
37 libdyld.dylib 0x00007fff204aef3d start + 1
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0xaaaaaaaaaaaaaaaa rbx: 0x00007f85fad8d190 rcx:
0x0000000000000001 rdx: 0x0000000000000000
rdi: 0x00007f85fad8d190 rsi: 0x00007f85fbe99490 rbp:
0x00007ffeefab3a90 rsp: 0x00007ffeefab3a80
r8: 0x00007f85f9d0a7d0 r9: 0x00007f85f9ea0c80 r10:
0x00000000033755c0 r11: 0x00000000ffd4a001
r12: 0x0000000101f59320 r13: 0x00007f85fad8c430 r14:
0x00007f85fad8c430 r15: 0x0000000000000000
rip: 0x00000001020079ad rfl: 0x0000000000010286 cr2: 0x0000700002ecdff8
Logical CPU: 2
Error Code: 0x00000000
Trap Number: 13
Thread 0 instruction stream:
48 20 0f 9f c2 b8 ff ff-ff ff 0f 4d c2 5b 41 5e H .........M.[A^
5d c3 90 55 48 89 e5 53-50 48 89 fb 48 8b 05 e0 ]..UH..SPH..H...
de 04 00 48 85 c0 75 24-48 8d 3d d4 de 04 00 e8 ...H..u$H.=.....
79 93 01 00 85 c0 74 14-e8 e6 eb ff ff 48 8d 3d y.....t......H.=
bf de 04 00 48 89 c6 e8-67 93 01 00 48 85 db 74 ....H...g...H..t
69 48 8b 35 ab de 04 00-48 8b 03 48 85 c0 74 05 iH.5....H..H..t.
[48]39 30 74 0c 48 89 df-e8 9c 94 01 00 85 c0 74 H90t.H.........t <==
49 48 8b 05 8b de 04 00-48 85 c0 75 24 48 8d 3d IH......H..u$H.=
7f de 04 00 e8 24 93 01-00 85 c0 74 14 e8 91 eb .....$.....t....
ff ff 48 8d 3d 6a de 04-00 48 89 c6 e8 12 93 01 ..H.=j...H......
00 48 8b 35 5b de 04 00-48 89 df e8 77 94 01 00 .H.5[...H...w...
8b 40 2c 48 83 c4 08 5b-5d c3 48 8d 3d 76 3f 02 .@,H...[].H.=v?.
Thread 0 last branch register state not available.
On 28/9/21 12:54, John Ralls wrote:
On Sep 27, 2021, at 6:47 PM, prl <p...@ozemail.com.au> wrote:
I seem to be consistently getting a Gnucash crash when I exit (using either
Gnucash>Quit or command-Q) from Gnucash 4.7-2 on my Big Sur MacBook Pro. Caused
by a Segmentation Violation.
Here's a snippet from the macOS log of the crash:
Process: Gnucash [4025]
Path: /Applications/Gnucash.app/Contents/MacOS/Gnucash
Identifier: org.gnucash.Gnucash
Version: 4.7-2 (4.7-2)
Code Type: X86-64 (Native)
Parent Process: zsh [4019]
Responsible: Terminal [4017]
User ID: 501
Date/Time: 2021-09-28 11:28:31.262 +1000
OS Version: macOS 11.6 (20G165)
Report Version: 12
Bridge OS Version: 5.5 (18P4759a)
Anonymous UUID: CA0735A3-3879-5356-BA71-4D9410666AF2
Sleep/Wake UUID: 9E59B9B4-5345-4236-BD83-17C01E85C186
Time Awake Since Boot: 8400 seconds
Time Since Wake: 7700 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 [4025]
I can post a full crash log as an attachment if it helps.
Any ideas, anyone?
System details:
Gnucash 4.7-2 for Intel MacOS >= 10.13, Build ID: 4.7+(2021-09-25)
macOS Big Sur 11.6
MacBook Pro (13-inch, 2019, Four Thunderbolt 3 ports), MacBookPro15,2
Please post the bit with the address and the first few lines of the stack
trace, enough to show at least 2 gnc_ functions.
Regards,
John Ralls
_______________________________________________
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.