why has my standalone zotero become too glitchy to use?
I have a late-2011 MacBook Pro with a fairly full 1T hard drive 16 GB RAM running OS 10.12.6; I'm using Firefox 61.0.1 and Zotero 5.0.54. I have a large number of Zotero records in 3 collections. Half the time I launch the application it hangs on Loading Items and never does load them. Other times, when I do get records in one collection, I can't change to another collection and have the items load. I have to close the application and relaunch it, with loading taking 5 minutes if it happens at all. Yes other applications aren't running as fast as they used to--I'm keeping this last of the 17 inch MacBook Pros because I am usually away from my office--but they all still work, except Zotero. I don't know what to do.
https://www.zotero.org/support/debug_output
And submit a Debug ID (it will start with D)
from a slow but successful move from one collection to another (3-4 minutes): D1836645253
from saving one firefox webpage, moving to a new folder in the same collection (1-2 min to load), saving a second webpage (manual entry of author's name not accepted), to "an error has occurred: please restart Zotero.": D1059186082
One thing you can try is restarting Zotero, letting it load completely, and then checking database integrity in the Advanced → Files and Folders pane of the Zotero preferences. That will actually additionally rebuild the database, which may improve the performance somewhat.
But there's clearly a problem here. The 2011 laptop and spinning hard drive are likely a part of it, but something else may be wrong, since you've now reported this a few times and we haven't received many recent reports of this.
840 MB also seems quite big for that number of items. What are the values for the full-text indexing settings and stats in the Search pane of the Zotero preferences?
So what happens now when you start Zotero? Can you provide a Debug ID for Zotero startup?
Indexed: 16519
Partial: 59
Indexed: 2215
Words: 496692
debug IDs in message 6 days ago
If you can provide a Debug ID that shows 1) collections not loading or 2) getting a restart error, that would give us info to debug this further.
I don't know what this refers to:
"Also we need the values of the full-text indexing settings, not just the stats."
maximum pages to index per file: 100
latest failure to load (after 15 minutes) has error report ID 845318017
In any case, my suggestion above still holds.