search

AllTheMods / All-the-mods-9-Sky

All the mods skyblock pack for 1.20.1 Forge
52 stars 39 forks source link

[Crash]: Failed to set real-time priority for thread: Operation not permitted #552

Open redkittty opened 2 months ago

redkittty commented 2 months ago

Possible Fixes

Yes

Modpack Version

1.0.8

What happened?

So basically I launch the game, after Forge says Minecraft Starting, the console prints this

#

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

#

SIGFPE (0x8) at pc=0x00007fb42d09fb4d, pid=385557, tid=386247

#

JRE version: OpenJDK Runtime Environment (Red_Hat-17.0.11.0.9-1) (17.0.11+9) (build 17.0.11+9)

Java VM: OpenJDK 64-Bit Server VM (Red_Hat-17.0.11.0.9-1) (17.0.11+9, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)

Problematic frame:

C [libopenal.so+0x9fb4d]

#

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/jason/.local/share/PrismLauncher/instances/All the Mods 9 - To the Sky - atm9sky/minecraft/core.385557)

#

An error report file with more information is saved as:

/home/jason/.local/share/PrismLauncher/instances/All the Mods 9 - To the Sky - atm9sky/minecraft/hs_err_pid385557.log

[thread 385558 also had an error] [ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1) #

If you would like to submit a bug report, please visit:

https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=java-17-openjdk&version=38

# Process crashed with exitcode 6.

Keep In mind I assigned 16gb of RAM out of my 32 so it couldn't have ran out of memory

Crash Log

https://gist.github.com/redkittty/c76da98170c82b35036bcd0cf5910141

Latest.Log

https://gist.github.com/redkittty/2972f0f9bb06cf3876102b7667a646db

Koupius commented 2 months ago

From the logs it looks like you are using Prism launcher, if that is the case please enable "Use system installation OpenAL" and include the directory to the OpenAL.dll file in the box below. If that does not work, you will need to create a ".alsoftrc " config file in your $HOME folder with the contents "devices=pulse".

TomSmithThe3rd commented 1 month ago

The following fixed this issue for me (linux only guide):

  1. ensure openal is installed using your preferred package manager. For me it was: sudo pacman -S openal

  2. create the .alsoftrc in your home directoy: touch ~/.alsoftrc

  3. open the file in your preferred text editor: nano ~/.alsoftrc

  4. add the following configuration

    [general]
drivers=pulse
hrtf=true

  5. reboot for good measure and test.