Skip to content
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

Closed
jonasfrede opened this issue Jun 4, 2018 · 7 comments

Comments

@jonasfrede
Copy link

jonasfrede commented Jun 4, 2018

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:

  1. Install the most recent java version to date from this page (which is 1.8.0_171 to date)
  2. Install JabRef 4.3 with the installer provided
  3. Start JabRef and see the error message that 1.8.0_172 is required, although 1.8.0_171 is the most recent available version

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?

@jonasfrede jonasfrede changed the title Minimum required java version for JabRef 4.3 is higher than the most recent stable java release provided for Windows 10 Minimum required java version for JabRef 4.3 is higher than the most recent stable java release provided for consumers on Windows 10 Jun 4, 2018
@tobiasdiez
Copy link
Member

Strange...Update 172 is actually available from http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html.

@bernhard-kleine
Copy link

bernhard-kleine commented Jun 4, 2018

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.
There should a warning to be aware that this might rise a problem. I would like to see the Jabref staff being proactive and not reactive in such a case.

my 5 cts

@omikro
Copy link

omikro commented Jun 4, 2018

Just the same with Debian Jessie. Any atempt to upgrade to 1.8.0_172 failed.

@bernhard-kleine
Copy link

bernhard-kleine commented Jun 4, 2018

Upgrading with the link thomas provided worked smoothly.

@omikro
Copy link

omikro commented Jun 4, 2018

Thanks

@hu00004
Copy link

hu00004 commented Jun 6, 2018

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??

@stefan-kolb
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants