Zotero quit unexpectedly on new 2021 MacBook Pro with M1pro

andrealagna
Hi, I installed Zotero on a new MacBook Pro and keep getting this "Zotero quit unexpectedly. Click reopen to open the application again. Click report to see more detailed information and send a report to Apple" when I tried to open it.

Anyone has the same issue?
  • dstillman
    Can you provide the first 100 or so lines of the crash log?
  • andrealagna
    -------------------------------------
    Translated Report (Full Report Below)
    -------------------------------------

    Incident Identifier: D3115BA1-7895-4865-AA96-272E768A95FB
    CrashReporter Key: 4F3B222B-28CC-4351-8E04-81321D86D0C9
    Hardware Model: MacBookPro18,3
    Process: zotero [43082]
    Path: /Applications/Zotero.app/Contents/MacOS/zotero
    Identifier: org.zotero.zotero
    Version: 5.0.96.3 (5.0.96)
    Code Type: X86-64 (Native)
    Role: Background
    Parent Process: launchd [1]
    Coalition: org.zotero.zotero [18523]

    Date/Time: 2021-11-05 16:59:37.2522 +0000
    Launch Time: 2021-11-05 16:59:32.3719 +0000
    OS Version: macOS 12.0 (21A344)
    Release Type: User
    Report Version: 104

    Exception Type: EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000001, 0x00007ff7ffe84af0
    Exception Note: EXC_CORPSE_NOTIFY
    Termination Reason: SIGNAL 5 Trace/BPT trap: 5
    Terminating Process: exc handler [43082]

    Triggered by Thread: 0

    Application Specific Information:
    rosetta error: /var/db/oah/279281322164224_279281322164224/6267dc97522dce9ad906c24a2b578dec6c6375e019cf7d666fbe55cd71d2de85/zotero.aot: attachment of code signature supplement failed: 1


    Thread 0 Crashed:
    0 runtime 0x7ff7ffe84af0 0x7ff7ffe68000 + 117488
    1 runtime 0x7ff7ffe84b38 0x7ff7ffe68000 + 117560
    2 runtime 0x7ff7ffe7b438 0x7ff7ffe68000 + 78904
    3 runtime 0x7ff7ffe7c510 0x7ff7ffe68000 + 83216
    4 runtime 0x7ff7ffe7bc8c 0x7ff7ffe68000 + 81036
    5 runtime 0x7ff7ffe6bac0 0x7ff7ffe68000 + 15040
    6 ??? 0x3 ???


    Thread 0 crashed with ARM Thread State (64-bit):
    x0: 0x0000000000000000 x1: 0x0000000000000003 x2: 0x000000000000003c x3: 0x000000000000002c
    x4: 0x0000000000000303 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x0000000000000000
    x8: 0x00007ff7ffea3000 x9: 0x0000000000000000 x10: 0x0000000000000000 x11: 0x00007ff7ffea3949
    x12: 0x0000000000000000 x13: 0x0000000000000000 x14: 0x0000000000000000 x15: 0x00007ff7ffe8b828
    x16: 0xffffffffffffffe1 x17: 0x00000000ffffffff x18: 0x000000030a34404b x19: 0x00007ff7ffe992e1
    x20: 0x000000030a344700 x21: 0x0000000102f5f000 x22: 0x0000000000000004 x23: 0x0000000102f5f000
    x24: 0x0000000000000003 x25: 0x0000000000000001 x26: 0x000000030a343b60 x27: 0x00000002033c01b8
    x28: 0x000000030a34c930 fp: 0x000000030a342940 lr: 0x00007ff7ffe84ae8
    sp: 0x000000030a342920 pc: 0x00007ff7ffe84af0 cpsr: 0x60000000
    far: 0x000000030a342958 esr: 0xf2000001 (Breakpoint) brk 1

    Binary Images:
    0x7ff7ffe68000 - 0x7ff7ffe97fff runtime (*) <70e45ce2-97b7-333e-8cad-dad5f9ff28e9> /usr/libexec/rosetta/runtime
    0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???

    Error Formulating Crash Report:
    dyld_process_snapshot_get_shared_cache failed

    EOF
  • dstillman
    That just looks like a Rosetta bug. You should start by upgrading to macOS 12.0.1.

    Deleting the app from Applications and redownloading might also help.
  • andrealagna
    Thank you so much! :)

    It works now. I deleted the Zotero app, updated the software to 12.0.1, reinstalled the Zotero app.
  • warmgreycoolblue
    I'm having the same problem. I was running OS 12.0.1 when I downloaded Zotero. I tried deleting and re-downloading the app. Any other tips?
  • dstillman
    @warmgreycoolblue: Try restarting your computer.
  • frankweber
    edited January 18, 2022
    Same problem here. Since using a new macbook pro with M1 I keep getting this "zotero quit unexpectedly" - error. It always is shown when the laptop has not been used for some time, e.g. after lunch etc.


    see error info below:

    [unrelated output removed — D.S.]
  • dstillman
    We'd have to see the crash log (terminal output isn't relevant), but if it's the same as above, it would still just be a Rosetta bug. Make sure you're running 12.1, and if you are, hopefully it will be fixed in 12.2.
Sign In or Register to comment.