-
-
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
Seaching for bibliographies and importing them triggers uncaught java.lang.IndexOutOfBoundsException #7606
Comments
Threading issue with the biblatex cleanup action which is run after import. It somehow triggers listener on ClearField in the UI which are not run on the FX thread |
Update: the exception is triggered stably only when searching ArXiv, both with and without file download. Search other bibliography repositories (Medline, Crossref, DBLP, CiteSeerX) mostly goes without an exception. |
I think I found the root cause: The key problem is that peformSearch is itself executed in a Background Thread. jabref/src/main/java/org/jabref/logic/importer/fetcher/CompositeSearchBasedFetcher.java Lines 50 to 64 in bb011c9
|
Hi, I think this problem is interesting, could I try to fix it? |
* Fix threading cleanup in performSearch Fixes #7606 * Fix variable * use bibdatabase mode * cleanup is already done in import handler * Should fix 1018
JabRef version 5.2, 5.3, commit badffe9 in 'master' on LinuxMint-19.3, Linuxmint-20.1 -->
When search for literature (say in ArXiv) and the importing entries, an uncaught exception is triggered. This behaviour is not always present, but can be reproduced after searching and importing several times in the same session.
Steps to reproduce the behavior:
The bug might be related to #7343, but the exception is different (OutOfBounds instead NullPointer), and is not in the Dark mode.
Sometimes there are multiple exceptions happening opening multiple pop-up windows. The fate of JabRef after exception is different – sometimes it freezes and the process needs to be killed, sometimes one can still save the database after closing the exception popup. If JabRef can be closed via it interface, it reports numerous dowload threads still running in the bacground.
More screenshots with sporadic exceptions after the sequence of actions listed here are available in my server:
http://saulius-grazulis.lt/~saulius/JabRef/screenshots/
The log message, copied and pasted from the window, reads:
Log File
The text was updated successfully, but these errors were encountered: