-
-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Out of memory error on Windows #2748
Comments
You're actually running into #2315. I'm working on something that will relieve memory pressure, but that's a fair bit of work, and I don't know how long it will take. I see you've already turned off the cache, so short-term there's nothing that can be done about this (except moving to Zotero 7). |
The fix will be communicated on #2315, if you want to be kept updated, please join that issue. |
Hi, Thank you very much for the answer. I'll look at #2315 then. Good luck with the fix! (By the way, if the issue is about the memory i can just select a smaller portion of my library to be exported, i guess) |
I wanted to add a quick tip to solve this problem easily (up to a certain extent at least). The issue is related to memory, therefore reducing the data to export fixes it. So, instead of exporting your library by splitting it into different .bib files, you can export your library altogether but with less information for each database entry. Anyway, many fields will not even show up in your bibliography (e.g. the 'abstract' field). So i did the following:
|
Debug log ID
RCYJ3YSL-refs-euc/6.7.143-6
What happened?
This problem is really similar to that shown in: #1575
Steps to reproduce:
Expected behaviour:
exporting a .bib file for my whole library
Actual behaviour:
pop-up saying: "An error occurred while trying to export the selected file."
Notes
I tried to export each collection separately and no errors occur...
The text was updated successfully, but these errors were encountered: