-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Short freeze when selecting first entry after fresh start #8446
Comments
How long is the freeze? I also experience that whenever i click on an entry after starting Jabref there is a small lag even with very mall database (~ 20 entries), but this is negligible and is not new to 5.5, but also was present since at least 5.4. In order to open the entry editor, i have to click on an entry twice, not once, which could be designed intentionally, as there are features (e.g. pushing entry to external application) that do not need the entry editor. JabRef 5.5--2022-01-17--27a05c7 |
|
This freeze is probably caused by indexing linked and attached pdf files to optimize for full-text search. The more attached pdf files you have, the longer the indexing will take. In the newest development version, a preference was added to disable full-text indexing. Would you mind giving some feedback if this would work for you and report, if it solves the freeze? |
I will try to find some time to try out the new version. However, I noticed that when I start JabRef it starts a background task that is about indexing files and the freeze upon the first selected item occurs, even if I wait until that task has finished before selecting any of my entries. This makes me doubt that the freeze is due to the indexing 🤔 |
JabRef version
5.5 (latest release)
Operating system
GNU / Linux
Details on version and operating system
KDE Neon 5.23 (built on Ubuntu 20.04)
Checked with the latest development build
Steps to reproduce the behaviour
Appendix
Note: I didn't actually test the latest development version, but I had to check the boxes in order to submit this ticket. I currently do not have the time to look into getting any development versions to work
The text was updated successfully, but these errors were encountered: