Bug Description

A weird crash behavior while trying to load into a world.
Either caused by a mod ( since the crash was detected by the JRE ), or by a library.

Did this behavior use to work in the previous version?

Tried older versions, same crash logs.

Steps to Reproduce (for bugs)

1. Clean installation of the modpack.
2. Allocating 10204MB of ram.
3. Loading into the modpack.
4. Creating a new world.
5. Loading the world.
6. Before spawning it crashes.

Logs

• Client/Server Log: https://paste.atlauncher.com/view/8c062c4b-1bf0-47ac-82e9-dfcaa7a4fe00
• Crash Log: https://paste.atlauncher.com/view/8c062c4b-1bf0-47ac-82e9-dfcaa7a4fe00

Using the ATL one, since PasteBin flagged my attempts to upload the logs as spam.

Client Information

• Modpack Version: 3.2.3
• Java Version: 19.0.2
• Launcher Used: ATLauncher
• Memory Allocated:10204MB
• Server/LAN/Single Player: Singleplayer
• Optifine Installed: None
• Shaders Enabled: None

World Information

• Modpack Version world created in: 3.2.3
• Additional Content Installed: None

Can you please attach the error report mentioned in the log: **USERSDIR**/instances/SevTechAges/hs_err_pid15985.log

The log gives a cause for the crash (segmentation fault), but does not provide any context. The report should show what code was executing at the time of the crash and may help narrow down what native library is at fault.

Can you please attach the error report mentioned in the log: **USERSDIR**/instances/SevTechAges/hs_err_pid15985.log

The log gives a cause for the crash (segmentation fault), but does not provide any context. The report should show what code was executing at the time of the crash and may help narrow down what native library is at fault.

Sure.

I've uploaded it to Gist : https://gist.github.com/Bvddh4/0e87104ba30f719415354510732c6740
( I forgot about Gist, my bad, should've used it first )

Thanks, this is an issue with Antique Atlas that seems to crop up on certain Linux systems; I haven't been able to narrow down the exact cause but it seems to indicate something being weird about X and the selected default file chooser.

There is an easy fix; update Antique Atlas to the latest version for 1.12.2. This shouldn't impact anything else, but if you have any further issues please let us know.

Thanks, this is an issue with Antique Atlas that seems to crop up on certain Linux systems; I haven't been able to narrow down the exact cause but it seems to indicate something being weird about X and the selected default file chooser.

There is an easy fix; update Antique Atlas to the latest version for 1.12.2. This shouldn't impact anything else, but if you have any further issues please let us know.

That worked, and indeed I will come back if there are other issues.
Thank you.