LWJGL Forum

Please login or register.

Login with username, password and session length

Author Topic: Upgrade issues  (Read 124 times)

darkyellow

  • Newbie
  • *
  • Offline Offline
  • Posts: 21
Upgrade issues
« on: August 02, 2017, 05:46:07 »

Hi

I upgraded to the latest stable build from an old build (pre modular download), I deliberately unticked jemalloc. When running my app I now get the below error, it looks like it is trying to use jemalloc regardless of me not choosing it.

Code: [Select]
[LWJGL] [WARNING] Mismatch detected between the Java and native libraries.
java.lang.UnsatisfiedLinkError: org.lwjgl.system.MemoryAccessJNI.malloc()J
at org.lwjgl.system.MemoryAccessJNI.malloc(Native Method)
at org.lwjgl.system.MemoryAccessJNI.<clinit>(MemoryAccessJNI.java:29)
at org.lwjgl.system.Pointer.<clinit>(Pointer.java:22)
at org.lwjgl.system.MemoryAccess$MemoryAccessorUnsafe.getAddressOffset(MemoryAccess.java:140)
at org.lwjgl.system.MemoryAccess$MemoryAccessorUnsafe.<clinit>(MemoryAccess.java:131)
at org.lwjgl.system.MemoryAccess.getInstance(MemoryAccess.java:31)
at org.lwjgl.system.MemoryUtil.<clinit>(MemoryUtil.java:61)
at org.lwjgl.system.MemoryStack.<init>(MemoryStack.java:60)
at org.lwjgl.system.MemoryStack.create(MemoryStack.java:79)
at org.lwjgl.system.MemoryStack.create(MemoryStack.java:70)
at java.lang.ThreadLocal$SuppliedThreadLocal.initialValue(ThreadLocal.java:284)
at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:180)
at java.lang.ThreadLocal.get(ThreadLocal.java:170)
at org.lwjgl.system.MemoryStack.stackGet(MemoryStack.java:605)
at org.lwjgl.system.MemoryStack.stackPush(MemoryStack.java:614)
at org.lwjgl.system.Callback.<clinit>(Callback.java:38)
at org.darkyellow.engine.application.lwjgl.LwjglApplication.<init>(LwjglApplication.java:54)
at org.darkyellow.viewer.ViewerDesktop.<init>(ViewerDesktop.java:34)
at org.darkyellow.viewer.ViewerDesktop.main(ViewerDesktop.java:48)
[LWJGL] [MemoryAccessor] Unsupported JVM detected, this will likely result in low performance. Please inform LWJGL developers.
An exception has occured in the DarkYellow library
java.lang.UnsatisfiedLinkError: org.lwjgl.system.jni.JNINativeInterface.GetDirectBufferAddress(Ljava/nio/Buffer;)J
at org.lwjgl.system.jni.JNINativeInterface.GetDirectBufferAddress(Native Method)
at org.lwjgl.system.MemoryAccess$MemoryAccessor.memAddress0(MemoryAccess.java:56)
at org.lwjgl.system.MemoryUtil.memAddress0(MemoryUtil.java:535)
at org.lwjgl.system.MemoryUtil.memAddress(MemoryUtil.java:568)
at org.lwjgl.system.MemoryUtil.memAddress(MemoryUtil.java:556)
at org.lwjgl.system.MemoryStack.<init>(MemoryStack.java:60)
at org.lwjgl.system.MemoryStack.create(MemoryStack.java:79)
at org.lwjgl.system.MemoryStack.create(MemoryStack.java:70)
at java.lang.ThreadLocal$SuppliedThreadLocal.initialValue(ThreadLocal.java:284)
at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:180)
at java.lang.ThreadLocal.get(ThreadLocal.java:170)
at org.lwjgl.system.MemoryStack.stackGet(MemoryStack.java:605)
at org.lwjgl.system.MemoryStack.stackPush(MemoryStack.java:614)
at org.lwjgl.system.Callback.<clinit>(Callback.java:38)
at org.darkyellow.engine.application.lwjgl.LwjglApplication.<init>(LwjglApplication.java:54)
at org.darkyellow.viewer.ViewerDesktop.<init>(ViewerDesktop.java:34)
at org.darkyellow.viewer.ViewerDesktop.main(ViewerDesktop.java:48)
Logged

Kai

  • Guest
Re: Upgrade issues
« Reply #1 on: August 02, 2017, 07:24:17 »

[LWJGL] [WARNING] Mismatch detected between the Java and native libraries.

This means your classpath (and/or java.library.path) contains different versions of LWJGL Jars and Natives. Do not use java.library.path with LWJGL3, and make sure that you really only have the newly downloaded LWJGL jars in your classpath and not some older jars.
Logged

darkyellow

  • Newbie
  • *
  • Offline Offline
  • Posts: 21
Re: Upgrade issues
« Reply #2 on: August 02, 2017, 20:20:53 »

Thanks Kai! I feel a bit stupid, I glanced at the stacktrace and immediately saw the calloc command and thought there might be a packaging issue with investigating much at all. It turned out to be an invalid link to one of the natives jar. Its all fixed now so thanks again.
Logged