java.lang.NullPointerException: A required function is missing: glfwInitAllocator

[XoXoGameWolf]

With the steam directory of AOC3, game.jar extracted and AOC3-Source.jar extracted, running the DesktopLauncher class always returns the following log (I don't know much about MD formatting sry):

[JAVA] [AnalyticalEngine] Current working directory: /home/wolf/.local/share/Steam/steamapps/common/Age of History 3
[JAVA] [AnalyticalEngine] [DEBUG] Waiting for application to be initialised ...
[JAVA] [AnalyticalEngine] Loaded 24 files present in /AnalyticalEngine/JS
[JAVA] [AnalyticalEngine] Loaded 11 files present in /AnalyticalEngine/Config
[AnalyticalEngine] [ERROR] {
}
[AnalyticalEngine] Stack trace: Error
at error (:81)
at timeout_thread (:83)
[JAVA] [AnalyticalEngine] Loaded 57 files present in /AnalyticalEngine/GameFramework
[JAVA] [AnalyticalEngine] Loaded 0 files present in /AnalyticalEngine/Editor
[JAVA] [AnalyticalEngine] Loaded 18 files present in /AnalyticalEngine/Logic/Conditions
[JAVA] [AnalyticalEngine] Loaded 1 files present in /AnalyticalEngine/Logic/Effects
[JAVA] [AnalyticalEngine] Loaded 2 files present in /AnalyticalEngine/Logic/Parsers
[JAVA] [AnalyticalEngine] Loaded 6 files present in /AnalyticalEngine/Logic/Scopes
Exception in thread "main" java.lang.ExceptionInInitializerError
at org.lwjgl.glfw.GLFW.nglfwSetErrorCallback(GLFW.java:1255)
at org.lwjgl.glfw.GLFW.glfwSetErrorCallback(GLFW.java:1288)
at com.badlogic.gdx.backends.lwjgl3.Lwjgl3Application.initializeGlfw(Lwjgl3Application.java:85)
at com.badlogic.gdx.backends.lwjgl3.Lwjgl3ApplicationConfiguration.getDisplayMode(Lwjgl3ApplicationConfiguration.java:219)
at aoc.kingdoms.lukasz.jakowski.desktop.DesktopLauncher.main(DesktopLauncher.java:81)
Caused by: java.lang.NullPointerException: A required function is missing: glfwInitAllocator
at org.lwjgl.system.APIUtil.requiredFunctionMissing(APIUtil.java:129)
at org.lwjgl.system.APIUtil.apiGetFunctionAddress(APIUtil.java:122)
at org.lwjgl.glfw.GLFW$Functions.(GLFW.java:42)
... 5 more
[JAVA] [AnalyticalEngine] [DEBUG] 'application' initialised ...

This only happens once I add Analytical Engine. The game runs perfectly fine with just AOC3. I'm probably missing out on something stupidly easy, but the instructions on the page aren't very clear.

[XoXoGameWolf]

Also I use Arch Linux, if that adds anything

[LunatiK-ExpiX]

Same issue, installing glfw-git to see if that helps (It did not)

[XoXoGameWolf]

Well clearing out the solutions that don’t work helps to find the solutions that do work

[Confoederatio]

Alright, since we know that the game runs fine with just AOC3 (You should also check with the MP build of the game, since whether it varies between an executable and .jar can change on the Steam installation).

My best guess is that there is a change in the DesktopLauncher between how it was originally written and the decompiled code by FernFlower, and there is now a stack that triggers GLFW. So either a manual build of the .jar has to be done (see Instructions), and you can try running it with IntelliJ IDEA ironically itself only Windows-supported, but ports for Arch do exist - then manually tinker with the DesktopLauncher class itself to see what might be going wrong.

Ultimately, I'm still working on core functionality so I haven't moved onto cross-compatibility yet - but I'll put this on backlog until I can virtualise a bunch of operating systems and then test each one.

[XoXoGameWolf]

Along with your fix with GLFW compiling fix in the Steam comments, I got the program working, although it crashes with a fatal error at the very end of the program with the following:

A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x00007689448b0dde, pid=516177, tid=516225

JRE version: OpenJDK Runtime Environment (23.0.2) (build 23.0.2)
Java VM: OpenJDK 64-Bit Server VM (23.0.2, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
Problematic frame:
C [libEGL_nvidia.so.0+0xb0dde]

Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /home/wolf/.local/share/Steam/steamapps/common/Age of History 3/core.516177)

An error report file with more information is saved as:
/home/wolf/.local/share/Steam/steamapps/common/Age of History 3/hs_err_pid516177.log

If you would like to submit a bug report, please visit:
https://bugreport.java.com/bugreport/crash.jsp

Aborted (core dumped)

[Confoederatio]

It's a Linux-specific segfault (SIGSEGV) on NVIDIA Vulkan, so I imagine it has something to do with graphics drivers. It's happening at the C-level and I imagine it has to do with actually aborting the process post-recompilation. So my guess is either it has to do with:

1. I'm technically starting AnalyticalEngine on an unsupported JNI, at least in current builds.
2. Specific issues after recompilation (probably to do with that configuration of GLFW being out of sync with your Nvidia driver). You can look at the dump: /home/wolf/.local/share/Steam/steamapps/common/Age of History 3/hs_err_pid516177.log which contains low-level information to see if the application was correctly cleaned up.

Try running vulkaninfo and seeing what comes out, and if there's a segfault on that.

You can try updating your NVIDIA driver to see if that fixes anything, but hopefully for now it's just an inconvenient display error, but I'll see what I can do to resolve it.

[XoXoGameWolf]

No error. Just displays a bunch of GPU info. I do have a project I'm working on that uses GLFW, and I never get any errors with that, so I don't think it's anything like that. It could somehow be a bug with LWJGL, GLFW, or the actual nvidia drivers (although i doubt the last one)

Anyways it doesn't affect anything at all, just an annoying error at the end of the program, and repetitively adding logs to the directory. Speaking of, I'm pretty sure that you have a crash log laying around in the github code's root directory

[Confoederatio]

Yeah, so the *.log wasn't added to the .gitignore earlier on, and that was a file oversight from earlier testing. It's not relevant to current cases on Windows 11 which is my main dev environment.

[XoXoGameWolf]

Also, I forgot to mention, but if I use alt+f4 instead of pressing the exit button, then it doesn't have a memory leak.