-
-
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
Minimum required java version for JabRef 4.3 is higher than the most recent stable java release provided for consumers on Windows 10 #4093
Comments
Strange...Update 172 is actually available from http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html. |
This is obviously an issue of Oracle's Update policy. Two updates were simultaneously distributed, 171 and 172. On Win7 it is the same as on Win10. The higher Update is not provided automatically to customers. @tobiasdiez whether it is available or not is not the question. That it is not distributed is the problem. Do you expext anybody to update java to run Jabref? That is really the problem for customers. They have to do update manually and not via the usual procedure. my 5 cts |
Just the same with Debian Jessie. Any atempt to upgrade to 1.8.0_172 failed. |
Upgrading with the link thomas provided worked smoothly. |
Thanks |
However, in mac, the recommended version for java is still 1.8.0_161 (java 8 update 161). Dont know how to set it , and of course jabref can works even with the warning of updating java.. thus maybe no need to update java?? |
The java version contains a bug that raises CPU load continuously to 15-30 %. This will heat up your PC, and also causes concurrency problems for JabRef unfortunately. |
JabRef version 4.3 on Windows 10 x64
This issue seems like a small increment error which was introduced in JabRef 4.3 (see the first line here)
Steps to reproduce:
The problem is, 1.8.0_171 and 1.8.0_172 were released simultaneously, shown here and here.
Version 1.8.0_171 does not update to 1.8.0_172 automatically, even after checking for new updates in the scheduler, so my question is: Does the CPU leak described in 3943 still persist in 1.8.0_171 or should JabRef support both versions?
The text was updated successfully, but these errors were encountered: