Zotero Connector conflicts with SingleFile extension in chromium-based browsers.

When Zotero Connector is enabled, saving a webpage using the SingleFile extension (https://chromewebstore.google.com/detail/singlefile/mpiodijhokgodhhofbcjdecpffjipkle) will take forever, and the CPU usage will max out. I have to disable Zotero Connector in chrome://extensions/, in order to use SingleFile to save a webpage.

Could you please fix this? Thanks.
  • edited June 12, 2024
    I'm not seeing that (e.g., trying to save this page). Can you provide a URL on which you can reproduce that?

    When testing this, be sure to disable all extensions other than those two and reload the page in question.
  • edited June 12, 2024
    I'm experiencing the same issue, with identical symptoms. I've posted about it here: https://forums.zotero.org/discussion/115140/twitter-medium-snapshots-are-completely-broken-other-connector-issues (naturally, downgrading to a manifest v2 version of the extension fixes the issue)

    Yes, saving this page works, but lots of other pages fail, like articles on Medium. Try this one: https://phaylen.medium.com/the-15-most-beautiful-animals-in-the-world-ea92b2a03a4e

    SingleFile will get stuck on "Deferred images", seemingly forever. Network activity in DevTools shows what seems to be an infinite loop, with lots of cancelled requests for Zotero Connector's translateSandbox.html

    Browser: Google Chrome Version 126.0.6478.57 (Official Build) (64-bit)
    Zotero Connector version: 5.0.128
    SingleFile version: 1.22.49

    The browser is a clean installation, with a completely empty profile. Zotero Connector and SingleFile are the only extensions
  • This page works, but many other pages don't. For example, any job page at jobs.ac.uk, such as https://www.jobs.ac.uk/job/DIA046/senior-lecturer-associate-professor-in-ux-engineering, won't work:



    Zotero Connector is taking up almost all CPU resource. And upgrading to the latest Zotero Connector version 5.0.129 STILL can NOT fix this issue.

    So could you please have a closer look at this issue? Many thanks.
  • We've submitted 5.0.130 with a fix for this issue. It should be available within the next day, once Google approves it. Thanks for reporting.
  • @testplayer, @hackbunny: 5.0.130 is out now with the fix. Thanks again.
Sign In or Register to comment.