Trouble since update Zotero 8
This morning Zotero updated to Zotero 8. Since then, I have been having problems with the programme. When I highlight texts in my documents and add a comment to it, the programme crashes. Are there other users experiencing this issue as well?
Upgrade Storage
Can you say more about exactly what you're doing and what's happening?
See Reporting Problems for the two things we always need in order to help.
This happens consistently and makes it impossible to annotate PDFs properly.
Report ID: 449734741
Does this happen for all PDFs or only some?
This happens to all my PDFs.
Here’s the new debug ID, exactly as you told me to get it. Could you please give me a more detailed explanation of what I should do, in case this still isn’t correct? I also don’t think this is a feature that many people use, so it’s possible it hasn’t been reported by others yet.
I'm really doing my best to figure this out and provide the information you need. I’m trying to help get the program working properly, not make things difficult. Could you please stay polite as well?
When I follow the exact steps:
I enable troubleshooting mode (Help → Debug Output Logging → Restart with Logging Enabled…)
Zotero restarts
I create a highlight and add a comment
Before Zotero freezes/crashes, I click: Help → Submit Debug Output Logging → ‘Submit Output’
After I click ‘Submit Output’, I get a code that I can copy to my clipboard: D2086178140
Is this the Debug ID you’re asking for? If not, what exactly is missing or different from what you need?
I’m genuinely trying to provide the correct information so you can diagnose the issue
But I'm confused: you said it freezes when you add the comment, which is why I asked for output up until right before you add it. But you're capturing the adding, which means it's not actually freezing immediately. So then how long after you add the comment before it freezes? Are you doing something else that makes it freeze? Or do you just not touch anything and it freezes shortly after?
Can you open the debug output window with Help → Debug Output Logging → View Output, position the window so you can see it alongside your Zotero window, and then reproduce the freeze, and when it freezes, take a screenshot of the debug window and post it here? That may show us additional logging from when it freezes.
If I stop after one sentence and it hasn’t frozen yet, and then continue working elsewhere in the document, it doesn’t suddenly freeze afterwards. It really only freezes while I’m typing in the comment.
I hope this is what you mean with the screenshot. I made it when the programme did not react any more, and just before i shut it down:
https://s3.amazonaws.com/zotero.org/images/forums/u18712802/99ryo28orlp68fus1k07.png
edit: still happens in zotero 9.0.6.
If I run
/Applications/Zotero.app/Contents/MacOS/zotero -ZoteroDebugText
from the terminal. I get the usual stuff like:
```
zotero(4)(+0000001): Item 4164 has not changed
zotero(3)(+0007551): Writing reader state to /Users/mrzi/Seafile/Meine_Bibliothek/PhD/zotero_data/storage/6XK42YKE/.zotero-reader-state
zotero(3)(+0009522): Starting full-text content processor
zotero(4)(+0000000): Registering notifier observer 'fulltext_tL' for [sync]
zotero(3)(+0015177): Checking for unprocessed full-text content
zotero(4)(+0000001): SELECT itemID FROM fulltextItems WHERE synced=2
zotero(3)(+0000001): No unprocessed full-text content found
zotero(3)(+0000000): Unregistering full-text content processor idle observer
zotero(3)(+0000000): Stopping full-text content processor
zotero(3)(+0021222): Getting contents of /Users/mrzi/Library/Application Support/Zotero/Profiles/rr187p5f.default/treePrefs.json
zotero(3)(+0000002): Writing column prefs of length 7041 to file /Users/mrzi/Library/Application Support/Zotero/Profiles/rr187p5f.default/treePrefs.json
JavaScript error: , line 0: Error: Failed to load resource://gre/modules/PlacesDBUtils.sys.mjs
zotero(3)(+0278855): Last backup of database 'zotero' was less than 1440 minutes ago -- skipping backup
zotero(4)(+0004953): SELECT itemID FROM items JOIN deletedItems USING (itemID) WHERE libraryID=? AND dateDeleted <= DATE('NOW', '-30 DAYS') [1]
```
Then I click on a highlight to update the comment associated to the highlight, zotero freezes and does not recover. No further output is printed to the terminal.
Therefore I am also not able to click on report error via the UI to get a Report or Debug ID.
After restart, I clicked view Debug output and it showed me:
```
1784471888484 addons.xpi WARN Force scan SCOPE_APPLICATION (app-builtin-addons location missing from XPIStates)
[JavaScript Error: "uncaught exception: undefined"]
[JavaScript Error: "TypeError: this.ownerGlobal.gBrowser.getTabForBrowser is not a function" {file: "chrome://global/content/elements/browser-custom-element.mjs" line: 932}]
getTabBrowser@chrome://global/content/elements/browser-custom-element.mjs:932:54
onPageHide@chrome://global/content/elements/browser-custom-element.mjs:958:27
appName => Zotero, version => 9.0.6 (ARM64), os => macOS 26.5, locale => en-US, extensions => Better BibTeX for Zotero (9.0.46, extension)
(3)(+0030292): Starting full-text content processor
(4)(+0000000): Registering notifier observer 'fulltext_Q2' for [sync]
(3)(+0031383): Getting contents of /Users/mrzi/Library/Application Support/Zotero/Profiles/rr187p5f.default/treePrefs.json
(3)(+0000003): Writing column prefs of length 7041 to file /Users/mrzi/Library/Application Support/Zotero/Profiles/rr187p5f.default/treePrefs.json
```
I have submitted this with Debug ID D399871595
Evidence (from sample output of the frozen process, 2393 samples taken):
2393 Thread main thread, all samples in same call chain
→ CopyAttributeValue → NSAccessibilityGetObjectForAttributeUsingLegacyAPI
→ ??? (in XUL)
??? (0x4db7e44) → 1534 samples
??? (0x4db6db0) → 1534
??? (0x4d9c390) → 1491
??? (0x4d9ba58) → 1461
??? (0x4d9b33c) → 657
??? (0x4c74750) → 557
??? (0x4c786a4) → 183 ... (same addresses recursing)
All 2393 samples are within a single CopyAttributeValue — Firefox's nsIAccessibleMacInterface::getAttributeValue() calls itself recursively 1500+ times without returning. This is an infinite recursion inside the prebuilt XUL binary (Zotero.app/Contents/MacOS/XUL), not in Zotero's own code.
Root cause: An internal infinite recursion in Firefox's compiled C++ accessibility handler, triggered when FullKeyboardAccessFocusRingEnabled is active on macOS and the user edits an annotation comment.
Fix: (For Mac) Add to your Zotero profile's user.js at path: ~/Library/Application\ Support/Zotero/Profiles/*.default/user.js:
user_pref("accessibility.force_disabled", 1);
This tells Firefox to skip registering its AX handler.