Uncaught exception occurred in Thread[#53,JavaFX Application Thread,5,main] (-> Run JabRef as Admin as a fix) #11151
Comments
|
Can you please try the version from here? https://builds.jabref.org/jdk-ea/ |
|
It works when I run JabRef as administrator. However, this seems for me impractical. |
Siedlerchr
changed the title
|
Can you please tell me wich Windows version you are running exactly? e..g best to include the version string or build number |
|
Windows 10 Home |
|
Just tested on my other computer with Windows 10 Home 22H2 19045.4170 and it works fine. Do you have any accessibility stuff enabled? on screen keyboard of anything related? |
|
No, I am not using any accessibility stuff. |
|
It also has problems on the local disc. |
|
And the problem occurs when I want to add a new source. |
|
Let us know your graphics card, driver version and screen resolution if possible 😅 |
|
How do you add the source? New entry? copy pasting in the entry editor? |
|
Drag and drop to the collection, copy paste in the entry editor and name search in the entry editor.
Manual new entries work. But changing old entries also result in an error message.
|
|
I tried with auto completion enabled: Windows 11 ( @JanSeitz Wild guessing: Does resetting the preferences help? |
|
resetting perferences also doesn’t work.
I recognized that the titlebar shows “null” lwhen I start Jabref for a short time. In my memory that wasn’t the case before.
|
The |
|
Same problem here JabRef 5.13--2024-04-01--6bdcf63 Upon entering just two digits into the New Entry ->"Select Entry Type" -> DOI: java.lang.StringIndexOutOfBoundsException: Range [2, -2147483647) out of bounds for length 2 Running Jabref as Admin indeed works. |
|
Tested (as non-privileged user) |
|
I think, we are not the only ones in the world where this happens -- https://stackoverflow.com/q/78332309/873282 |
|
@dfw63 I assume you installed a Windows update? And JabRef worked before? Do you have your update history at hand? |
|
We should need if old versions of JabRef are affected. Does v5.11 (JavaFX 20) still work? |
|
We've been having the same issue in the Java app I work on. We'd never seen this issue at all until 24/03/24, and have seen an sudden increase since. We've using Java & JavaFX 17. The issue we believe is due to an Windows update, but have yet to be able to reproduce it ourselves, but have lots of customer that can. The issue also happens with Java 21 & JavaFX 21. We have an LTS relationship with Gluon and they have patched JavaFX for us to stop this from happening. |
Sorry, it is in German. Unfortunately I cannot exactly tell when the Jabref issue started for me. |
|
Current state: Tried to add a hotfix. Did try to use in JabRef, but did not succeed. Thus, we need to wait that someone reports to Oracle and that they fix it. |
|
@koppor can we use the reproducer for it? |
|
@Siedlerchr Does the reproducer have a text field? The MWE from SO is: // launch the application
public void start(Stage s)
{
// set title for the stage
s.setTitle("creating TextField");
// create a textfield
TextField b = new TextField();
// create a stack pane
StackPane r = new StackPane();
// add textfield
r.getChildren().add(b);
// create a scene
Scene sc = new Scene(r, 200, 200);
// set the scene
s.setScene(sc);
s.show();
}I think, simply adding a text field to the reproducer will show the error. |
|
There is now a JDK issue: https://bugs.openjdk.org/browse/JDK-8330462 |
|
@dfw63 Could you uninstall the recent update? Also das 2024-04 H2 update. Das ganz oben auf der Liste? - Das Ding ist, dass es hier auf meiner Kiste (AMD-Graphikkarte) läuft und ich hier im Blindflug rate, was es denn sein könnte :) |
|
@dfw63 Schreib mir auch gerne privat - Wir müssen irgendwie das konkrete Setup rausfinden, weil es bei der Mehrheit der Leute noch funktioniert. |
|
Please try the reproducer available at "Artifacts" at https://github.com/Siedlerchr/javafxreproducer/actions/runs/8718689729?pr=19. If it happens also there, we can enrich the reproducer to output more environment information to track down the issue. (PR creating these artifacts: Siedlerchr/javafxreproducer#19) |
|
Sorry, I cannot remove the latest 2024-04 H2 update right now. |
|
JabRef 5.14--2024-04-15--93e0174 On my machine the problem disappears as soon as I close the Deepl app (the program that allows you to open deepl typing Ctr-C twice). Once off, Jabref works normally. When on again, crash on entering DOIs or whatever again... Seems to be reproducible. |
|
@dfw63 Thank you so much for the reproducer. I could not resist and to post it on Mastodon: https://mastodon.acm.org/@koppor/112286143673069313. Now that the issue is reproducible, I am hoping for a fast fix. |
|
It is important to switch on/off the deepl app in the residential area (system tray, lower right corner). In jabref, I can even recover from the crash by closing the deepl app in the system tray, then getting back to it by opening the app again. Pretty funny. |
|
Proposed a fix at openjdk/jfx#1442. |
|
I can confirm that the problem in my case was related to the DeepL App. After removing this app, JabRef is working OK, and the problem with the Uncaught exception is gone. |
|
Please try out https://builds.jabref.org/jdk-ea/, it should be fixed there. |
|
Tested today, no issues any more. |
|
Thank you for reporting this issue. We think, that is already fixed in our development version and consequently the change will be included in the next release. We would like to ask you to use a development build from https://builds.jabref.org/main and report back if it works for you. Please remember to make a backup of your library before trying-out this version. |
JabRef version
Latest development branch build (please note build date below)
Operating system
Windows
Details on version and operating system
No response
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Using search and citationkey
Appendix
...
Log File
The text was updated successfully, but these errors were encountered: