Been getting a couple times "zotero quit unexpectedly" SIGSEGV messages since the last update.

Should I open an issue to Zotero’s github issue tracker?
  • edited September 21, 2021
    No, all reports go here.

    Nothing has changed in Zotero that would cause this. You don't say what macOS version this is or what Mac this is, but you should make sure you're running the latest version of macOS — in particular, there have been bugs in Rosetta on M1 Macs that have caused some crashes, but they should be mostly fixed in current versions.
  • I’m running Big Sur 11.5.2.

    However this made me think ; I recently added two add-ons:
    - scite Plugin for Zotero
    - Zotero Citation Counts Manager

    Any way to know if this could be related (except of course disabling them and waiting)?

    Crashes have been mostly happening when adding new items from the Zotero Safari Connector, but it doesn’t happen for every item (can’t see what the items that caused crashed had in common)
  • Can you provide the first 100 or so lines of the crash log (or email it to with a link to this thread)?
  • You should also update to 11.6.
  • I updated to 11.6 right after posting this actually and, dunno if it’s a coincidence, but no crashes since then. I’ll report back if it crashes again!

    Many thanks!
  • edited September 24, 2021
    Oh another crash. For what it’s worth — no idea if that’s reproducible or not — I was adding the following paper through Safari’s Connector add-on:

    I’m running MacOS Big Sur 11.6 (20G165), and Zotero 5.0.97-beta.46+4cfa23050

    Here is the MacOS "quit unexpectedly" report:


    Process: zotero [5859]
    Path: /Applications/
    Identifier: org.zotero.zotero-beta
    Version: 5.0.97-beta.46+4cfa23050 (5.0.97)
    Code Type: X86-64 (Native)
    Parent Process: ??? [1]
    Responsible: zotero [5859]
    User ID: 501

    Date/Time: 2021-09-23 15:48:58.462 -0400
    OS Version: macOS 11.6 (20G165)
    Report Version: 12
    Bridge OS Version: 5.5 (18P4759a)
    Anonymous UUID: E4BD3BE4-F0FF-AD2E-6F3E-A5D2F54AA3CB

    Time Awake Since Boot: 160000 seconds

    System Integrity Protection: enabled

    Crashed Thread: 0 Dispatch queue:

    Exception Type: EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x00007ffeee1f2ff8
    Exception Note: EXC_CORPSE_NOTIFY

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

    VM Regions Near 0x7ffeee1f2ff8:
    MALLOC_SMALL 7fa9bc800000-7fa9bd000000 [ 8192K] rw-/rwx SM=PRV
    --> STACK GUARD 7ffeea9f3000-7ffeee1f3000 [ 56.0M] ---/rwx SM=NUL stack guard for thread 0
    Stack 7ffeee1f3000-7ffeee9f3000 [ 8192K] rw-/rwx SM=SHM thread 0

    Thread 0 Crashed:: Dispatch queue:
    0 0x00007fff24c28827 CGSConnectionRegistryCheckConnectionID + 8
    1 0x00007fff24c2876b CGSConnectionByID + 247
    2 0x00007fff24c28dac CGSGetConnectionPortById + 34
    3 0x00007fff24c29e93 lookup_connection_port + 40
    4 0x00007fff24db1764 SLSCopySpaces + 42
    5 0x00007fff22fa6e17 getSpaces + 146
    6 0x00007fff23007712 _NSSpaceIsVisible + 25
    7 0x00007fff23766811 -[_NSFullScreenSpace _spaceConsideredVisible] + 70
    8 0x00007fff2376683d __45+[_NSFullScreenSpace visibleFullScreenSpaces]_block_invoke + 25
    9 0x00007fff22c8b52a _NSMapAndFilter + 226
    10 0x00007fff22c9c946 +[_NSFullScreenSpace visibleFullScreenSpaceOnScreen:] + 102
    11 0x00007fff22c9c897 -[NSScreen _menuBarHeight] + 76
    12 0x00007fff22c9c835 -[NSScreen _layoutFrame] + 71
    13 0x00007fff22cd5a23 -[NSScreen visibleFrame] + 44

    Thread 1:: Gecko_IOThread
    0 libsystem_kernel.dylib 0x00007fff20358c4a kevent + 10
    1 XUL 0x000000010451baaa 0x104029000 + 5188266

    [extra output removed — D.S.]


    (output trancated b/c of forum config)
  • That certainly looks like a macOS bug, so you might need to wait and try in Monterey.

    Are you doing something with Spaces and/or full-screen mode?
  • Zotero was in full-screen mode when the last bug happened. I often use it.

    Shouldn’t others experience this bug as well? I’ve seen no other reports. Maybe it’s the two plugins I’ve mentioned? Do you see anything related to those in the log?
  • edited September 24, 2021
    No, there've been no other reports that I can recall, though I don't think full-screen mode gets much use.

    Your best bet is seeing if it happens in Monterey next month.

    Zotero plugins shouldn't make a difference.
  • Avoided full-screen mode since the last two days ; no crash so far. You think it could be related?

    Is there some way I could help investigate this? With the new PDF reader I guess full screen mode might get more usage than it’s currently the case.
  • As I say, the best thing to do here is to see if it happens in Monterey next month. It appears to be crashing in macOS full-screen code, not in Zotero code.
  • Okay. Odd that it’s the only app I use that crashes in full-screen mode though. I’ll update this thread accordingly, thanks.
  • Still been avoiding full screen mode, no crashes since last week. Full screen mode indeed seems to be the culprit here.
Sign In or Register to comment.