Holographic Displays

Holographic Displays

3M Downloads

Startup error

Andre601 opened this issue ยท 8 comments

commented

Issue

My server crashed out of nowhere and after a restart does HolographicDisplays now throw this error here: https://paste.helpch.at/rojicamiwe.css

Additional information.

Server: PaperSpigot git-Paper-1478 (MC: 1.12.2) (Implementing API version 1.12.2-R0.1-SNAPSHOT)
Plugins: https://paste.helpch.at/osirukekac
Threat dump of the crash: https://paste.helpch.at/kahizasiki.sql

According to my host do they run OpenJ9 since a month (roughly)
The console provides this information on startup:

openjdk version "1.8.0_202"
OpenJDK Runtime Environment (build 1.8.0_202-b08)
Eclipse OpenJ9 VM (build openj9-0.12.1, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20190205_213 (JIT enabled, AOT enabled)
OpenJ9 - 90dd8cb40
OMR - d2f4534b
JCL - d002501a90 based on jdk8u202-b08)
commented

Multiple people on dev.bukkit report the same issues

Report-#412
Report-#414
Report-#415
Report-#417
Report-#418

commented

@Andre601 What's your HolographicDisplays version?

commented

Latest release which at this point is 2.3.2

commented

try to use the latest dev build from https://ci.filoghost.me

commented

I tried latest from the jenkins (2.3.3) but still receive this error.

commented

I think it's because some versions of OpenJDK block the use of java's internal API methods, and the plugin cannot "see" or use them, like OpenJ9 does here. There is the default method that only uses the public API, but is a bit slower since it does some useless calculations for the scope of HD.

This problem is specific to java 8 and lower, because java 9 has an API made for this.

It shouldn't have any real impact on performance, and there were no complaints before the new method was implemented.

commented

The error in reality is just a warning. The plugin works just fine, it means it cannot use a feature to speed up some things. It has been now disabled and will only show up in debug mode: 87fc7bd

commented

Okay. Thanks for that.

But what exactly causes this? Like I assume it's a missing thing that perhaps could be related to the server using OpenJ9?
Would really love to know what causes this and what could be a solution for the future.