Stuck when sliding PDF

After updating to beta 114, zotero has much higher pressure on single cpu core. So, the reaction of zotero, such as opening a new pdf or sliding pdf, is so slow
https://s3.amazonaws.com/zotero.org/images/forums/u6879818/rnhps6yg5nj6tu0euiym.png
  • Does this happen with all PDF files? OCRed PDF files might use more CPU resources.
  • All PDF files, not only OCRed. Mine is intel 9900k on windows platform. After manually downgrading to beta 99, things go better.
  • Could you update to 114 again and provide a Debug ID for it happening?
  • I updated and find the zotero goes quite smooth. I don't know why. The debug id is D1311636902
  • This time, the cpu usage get higher when sliding but lower when no action. Last time, the cpu usage was always on a high level.

  • Is it possible that Zotero was syncing your library at that time?
  • Thanks for your help. I will check what zotero is doing when the stuck happens again.
  • Getting this same issue on 7.0, Zotero is maxing out cpu (and increasing ram usage significantly) when scrolling.
  • @garbus

    1) What is the CPU usage when you stop scrolling compared to when you scroll?
    2) Does this issue occur with all PDF files?
    3) Does restarting Zotero help?
  • Thanks for the quick response, @martynas_b
    1) CPU usage when idle is 3.6% vs 200% when scrolling through a longer document (~20 pages). 200% refers to two cpu cores here I believe.
    2. I've reproduced this issue in multiple pdf files, but it seems more pronounced the longer the file is.
    3. Restarting zotero doesn't help
  • @garbus

    1) Can you test with all third-party plugins disabled, if you have any?
    2) Are the PDF files OCRed?
    3) Could you test CPU usage with a simple PDF file, like https://bitcoin.org/bitcoin.pdf?
  • edited August 15, 2024
    @martynas_b
    1) I'm fairly certain I have no plugins enabled.
    2) Some of pdfs are indeed OCRed.
    3) The bitcoin whitepaper is much easier on the CPU, only taking about 70% of one cpu core to scroll between top to bottom, however, a longer non-OCRed file easily goes past 150%.

    This is on an x86 machine running Linux.
  • @garbus

    Can you check if graphics acceleration in Settings → Advanced → Config Editor → layers.acceleration.disabled is set to false?
  • @martynas_b It was previously set to `false`, I just set it to `true` and tested again. Same behavior. I should note that when I'm done scrolling, the cpu goes back down to <10%.
Sign In or Register to comment.