-
-
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
Seemingly Random freeze on PDF import #2482
Comments
Can confirm this also occurs on v3.8.2 It appears to be a state issue as importing this PDF file caused a crash. However, when importing into a fresh database it did not cause a crash. Any hints on how to turn on file based logging on the release version would be much appreciated. |
Hi! Regarding the logging: We have not implemented a file based logging mechanism - but you can run the |
Hi @matthiasgeiger sure.
In the case of the error occurring the JabRef UI is unresponsive following (4) however there are no drawing errors. The window can be relocated and it redraws correctly. CPU usage for JabRef indicated at 0%, only way to close JabRef is via task manager. Thanks for the hint on running the jar version I'll try that and see if it provides some further clues |
As I cant reproduce that here, do you make use of the XMP feature, e.g. creating metatadat from the pdf or do you solely attach the pdf? |
That's correct, first one - I let JabRef pull out any XMP data, if the pdf doesn't contain any then I manually find the doi enter that and then use JabRef's "Get BibTex from DOI", and if no doi then I just copy paste bibtex from scholar.google.com when it doesn't halt I find this the quickest way to import and have the pdfs attached automatically (and renamed/relocated to a local directory). The unfortunate problem is that I also have difficulties reproducing this. |
@matthiasgeiger is there a way to set the log level when calling via the command prompt? I had the situation freeze occur but apart from the initial INFO level log no further details displayed. |
However, I fear that this is caused by a deadlock which will not be displaying any useful information on the console... (As reported in #2489 (comment)) |
Thanks @matthiasgeiger looks like it may be some bad timing / race condition on saving the database. Managed to capture this flurry of messages:
|
Thanks! We will try to check whether we can find the problem now! |
Right it has occurred sufficient number of times for me to get the code up and running in debug mode. It appears it is a deadlock as you feared so will add more details in #2489. |
+ Caused by attempt to update UI on multiple threads
* upstream/master: Fix error when path is no valid directory (#2527) French localization: translation of a string French menu: localization Highlight groups that match any/all of the entries selected in the main table. (#2515) Fix % sign cleanup (#2521) Revert "Fix repeated escaping of % sign" (#2520) Fix repeated escaping of % sign (#2519) fix for #2482 deadlock on PDF import (#2517)
v3.8.1, windows 10
Great work on this version the get BibTex from doi functionality is working better than ever. Unfortunately this version often seems to suffer a freeze when importing PDFs. Initially I thought it was caused by some interaction with the quality assured field as it seemed to freeze after setting a few quality assured fields and then importing a PDF. However, I've also had it freeze without setting those. On a restart it imports the file no problem so seems to be some state issue.
Would love to give more details but the freeze prevents me from accessing the in-app log. Is there a quick way to get it to print the log to a file without running in dev mode?
Perhaps related to #410 #2309
The text was updated successfully, but these errors were encountered: