Anki Crashing Due to Segmentation Fault

Hi everyone,

Hoping someone can help me with my Anki crashing. I have MacOS Big Sur 11.2.3 with an M1 chip and 8 GB memory. The app was working just fine on the current OS until yesterday, and now the app won’t open at all. The error I get when I try to open Anki is coped below (I had to abridge the error below due to character limitations on this post). It looks like a segmentation fault, but I have very minimal computer science knowledge. Would so appreciate any advice on how to fix this!

Process: anki [5507]
Path: /Applications/
Identifier: net.ankiweb.dtop
Version: 23.10 (0)
Code Type: ARM-64 (Native)
Parent Process: ??? [1]

Crashed Thread: 0 Dispatch queue:

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000edc000

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [5507]

VM Regions Near 0xedc000:

__TEXT 100edc000-103584000 [ 38.7M] r-x/r-x SM=COW /Applications/

Application Specific Information:
dyld: launch, running initializers

Thread 0 Crashed:: Dispatch queue:
0 net.ankiweb.dtop 0x0000000100fcdd68 malloc_conf_init_helper + 296
1 net.ankiweb.dtop 0x0000000100fcd70c malloc_init_hard_a0_locked + 140
2 net.ankiweb.dtop 0x0000000100fcd70c malloc_init_hard_a0_locked + 140
3 net.ankiweb.dtop 0x0000000100fd0d68 malloc_init_hard + 160
4 dyld 0x0000000103e4f77c ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 468
5 dyld 0x0000000103e4fb94 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 56
6 dyld 0x0000000103e4984c ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, char const*, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 620
7 dyld 0x0000000103e47300 ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 192
8 dyld 0x0000000103e473cc ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 96
9 dyld 0x0000000103e3284c dyld::initializeMainExecutable() + 220
10 dyld 0x0000000103e38b98 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 7388
11 dyld 0x0000000103e31258 dyldbootstrap::start(dyld3::MachOLoaded const*, int, char const**, dyld3::MachOLoaded const*, unsigned long*) + 476
12 dyld 0x0000000103e31038 _dyld_start + 56

Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000001 x3: 0x000000016ef1f780
x4: 0x000000016ef1f370 x5: 0x00000001a4797700 x6: 0x4000000000000000 x7: 0x7000000000000000
x8: 0x0000000000edc000 x9: 0x0000000100fcdcc0 x10: 0x0000000000000000 x11: 0x00000002123b7c06
x12: 0x00000002123b7c06 x13: 0x000000000000002b x14: 0x0000000000000881 x15: 0x000000000000000c
x16: 0x00000001a47975a0 x17: 0x0000000103e50f74 x18: 0x0000000000000000 x19: 0x00000001034bb75c
x20: 0x0000000000000001 x21: 0x000000016ef1f370 x22: 0x000000016ef1f780 x23: 0x0000000000000001
x24: 0x0000000103234476 x25: 0x00000001034bb75c x26: 0x0000000103234471 x27: 0x000000016ef1f928
x28: 0x0000000100fcd0e8 fp: 0x000000016ef1d8f0 lr: 0x0000000100fcd70c
sp: 0x000000016ef1d820 pc: 0x0000000100fcdd68 cpsr: 0x80000000
far: 0x0000000000edc000 esr: 0x92000006

                            VIRTUAL   REGION 

REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Kernel Alloc Once 32K 1
MALLOC 137.2M 11
MALLOC guard page 96K 5
MALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)
Stack 8176K 1
__AUTH 507K 110
__AUTH_CONST 7687K 246
__DATA 6172K 235
__DATA_CONST 8891K 244
__DATA_DIRTY 547K 89
__LINKEDIT 482.7M 4
__OBJC_CONST 1024K 90
__OBJC_RO 64.5M 1
__OBJC_RW 2544K 1
__TEXT 199.5M 261
__UNICODE 588K 1
shared memory 16K 1
=========== ======= =======
TOTAL 1.3G 1304
TOTAL, minus reserved VM space 975.3M 1304

A new release that fixes this should be out within a few days, you can use the pre-release in the mean time. Updating to something newer than Big Sur should also fix it.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.