Since Update Extreme Lag - Debug ID D1190699140

edited 20 days ago
Since installing the most recent update (7.0.15) Zotero on MacOS (14.6.1) is totally unusable the lag when scrolling is extremely bad, the CPU seems very high (>500% see image). This is very similar to what happened previously that was fixed but for now my Zotero is unusable. I am only trying to read a single 11 page PDF with no images. This may also be a result of 7.0.14 as I updated these only yesterday.

Opening in troubleshoot mode seems to resolve the issue but disabling plugins in normal mode does not.

On an aside, the better notes issue that I had with crashing when loading files with a lot of notes appears to be resolved.


https://s3.amazonaws.com/zotero.org/images/forums/u8744031/ofb24nqo3nroinz2fm3y.png
  • Does it happen in Troubleshooting Mode (Help -> Restart in Troubleshooting Mode)?
  • @adomasven sorry I did edit my original post to add that detail as I felt it would be useful.

    No it does not happen in trouble shooting mode but does happen with all plugins disabled
  • edited 20 days ago
    You have your Zotero data directory in cloud storage, which Zotero would've warned you not to do. Whether or not that's causing this, we can't help you further here as long as that's the case.

    https://www.zotero.org/support/kb/data_directory_in_cloud_storage_folder
  • @dstillman thanks for your reply. This is a locally stored folder that has been exactly the same for 4 almost 4 years. The file is not accessed anywhere except via Zotero and the only thing that has changed is the Zotero update. It works perfect in every other way and perfectly in troubleshooting mode. Unfortunately this is a Zotero issue and not a file directory issue.
  • It doesn't matter — it's in a clearly identified cloud storage path. If you'd like our help in these forums, you'll need to move it out and provide another Debug ID.
  • I have moved the data directory as requested and the system is performing exactly the same with extreme lag. I have included 3 debug IDs that hopefully shed some light on the issue

    1) D374331179 - Normal mode all plugins active, Auto sync off
    2) D1094739254 - Normal mode all plugins disabled, Auto sync off
    3) D1005661000 - Troubleshooting mode

    Only when in troubleshooting mode does Zotero perform normally.
  • Can you disable all plugins and provide a Debug ID for Zotero startup through reproducing the issue, using the "Restart with Logging Enabled…" option?
  • edited 18 days ago
    Debug ID of start up D839612241 sorry I didn't get it to reproduce - apologies
  • edited 18 days ago
    That shows a normal startup. What exactly did you do to reproduce the issue there, and what did you see? [OK, saw your edit.]

    Note that it would be normal for Zotero to use some CPU when it first starts up. After the initial auto-sync finishes, CPU usage should go down to ~0% when Zotero is idle.
  • I find it normally starts up fine and after 5-10 minutes it starts to lag or starts to use serious amounts of CPU. I will leave it logging now and see if I can recreate the issue and share the ID with you again.

    I really appreciate your help with this.
  • edited 18 days ago
    So I restarted with logging enabled and I re-enabled the BetterNotes plugin and that has immediately recreated the issue so I suspect the issue lies with BetterNotes integration somewhere. This also causes menus to disappear before being able to click on them

    D1541483645

    Restarted again with logging enabled and BetterNotes disabled and working fine (D1526090937).
  • For problems with a plugin, you'll need to contact the plugin developer.
  • Thanks for your help! I have just disabled the plugin it’s caused a few issues recently with Zotero updates. It’s a nice plugin but Zotero itself is much more important … really love the program you guys have developed and the support is first class. Thanks again
  • Hi @mdugganmrcvs , it would be helpful if you could create an issue in the plugin's repo (https://github.com/windingwind/zotero-better-notes) with the debug output.

    The plugin you mentioned above has some background activities if you set up the note <-> markdown syncing. If that's the case, try to disable the auto-syncing.
Sign In or Register to comment.