Upgrade Storagehackbunny
About
- Username
- hackbunny
- Joined
- Roles
- Member
Comments
-
@dstillman: the issue no longer reproduces. I don't know what changed, but that exact search is now almost instant, *and* it finds what it's supposed to. What I did was lowering full text cache limits (50000000 maximum characters, 10000 maximum page…
-
Situation is pretty bad at the moment, search is basically unusable now. Any query takes a very long time and it's a crapshoot whether it will actually search something or run out of memory and then leak a lot of memory This did not use to happen u…
-
D1461979477 This was the original search query that I mentioned in the OP: it should match a document that I archived yesterday, but it runs for a long time, allocates several GBs of memory, and then throws a NS_ERROR_OUT_OF_MEMORY error. After thi…
-
Excellent news, that's a huge relief. Thank you
-
I noticed, yeah. And yes, they're identical I guess I'll get used to using the item selector, which I never liked much
-
It's the main way I use Zotero Connector, as you'll note from the several bugs in that functionality that I reported in the past two days I just don't use it on Google Scholar because I only use Google Scholar for their citations, which often have …
-
The "extremely slow and complex" flow is importing from inside Zotero, by the way I never used Save to Zotero for Google Scholar because I was unaware that it worked in Google Scholar, while exporting EndNote citations worked perfectly
-
I was unaware that this had never been a recommended way of working on Google Scholar. I just discovered this functionality by experimentation or by accident, and it became part of my workflow I really wish that features lost in the upgrade to MV3 …
-
@dstillman: Good to know, one less thing to worry about
-
Same error here: [JavaScript Error: "Error: Service worker (re)started at 2024-06-13 00:01:52 at Object.initGlobal (chrome-extension://ekhagklcjbdpajgpjgmbionohlpdbjgc/zotero.js:182:20)"] No example URL needed, the error also occurs with no op…
-
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 o…
-
Downgrading to 5.0.124 (unpacked debug build), unsurprisingly, fixes *all* issues (Twitter snapshot, Medium snapshot, Ctrl-Shift-S shortcut, SingleFile conflict), but it also downgrades the extension to manifest v2, which will reach EOL soon
-
Downgrading to 5.0.124 (unpacked debug build), unsurprisingly, fixes the issue, but it also downgrades the extension to manifest v2, which will EOL soon
-
Stand-alone SingleFile (version 1.22.49) works, for what it's worth. That is, it would work if Zotero Connector didn't break it, sending it in an apparent infinite loop edit: I posted details here: https://forums.zotero.org/discussion/comment/46553…
-
Medium is also broken. If I save a members-only story reached through a Friend Link, I receive a snapshot of the paywall. Zotero Connector no longer saves what I see on screen and this is extremely concerning. Virtually unusable