-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Performance issue in Jabref5.1 using "search" function to find specific records #6824
Comments
Same here: my 5.1 version gets unresponsive (or very slow) during searches. JabRef 5.1--2020-08-30--e023aa0 |
On my Windows machine I have the same problem. The current JabRef version becomes almost unusable there. After hitting a search term CPU usage goes up to 90% and never drops again.
|
The problem persists in the current master. At the moment, I can't use either JabRef 5.1 oder 5.2 because of this problem. I have to kill (closing jabef is not enough - see picture) the program after each search on my ubuntu and my windows machine. I did a quick test with the testjabref.bib - it causes the same problem - so its not related to my bib file Strange, however, that it doesn't affect all users. |
Try disabling Autocomplete in the Preferences, many user reported that this helped |
Wow. That helped immediately! Thank you @Siedlerchr. I hope, auto completion is disabled by default. |
Thanks @Siedlerchr , disabling autocomplete helped directly. |
Solved for me too, big save |
issue is still relevant |
JabRef version
JabRef-5.1.msi
I just installed the new Jabref5.1 to see how it works with my literature.bib database that is about 29,900 Kb in size.
The database loads and shows pretty fast, a major improvement on some earlier 5.1 development versions :-)
However, when I try search on authors, the program seems to enter in a "never-ending loop" and becomes non-responsive whilst at the same consuming 95-97% of my CPU. I experienced the same problem in earlier 5.1 development versions. So I reversed to using "JabRef 5.0-beta.10--2019-12-16--aa6cbb7". In this development version, a search on author(s) is also slow, but the program does not become unresponsive.
Am using Windows10 Pro 64 bit on a Lenovo P700 with Intel Xeon E5-2603 @ 1.6 Ghz and 16 Gb RAM.
I am not a computer programmer and am not sure this is the feedback you need. If you need more technical details from me then please instruct me what I need to do to share these back to you.
Ed
The text was updated successfully, but these errors were encountered: