Unfortunately don't have any specific context or reproduction of how this happens, but occasionally a report comes by of an FTB SB4 instance crashing on initial loading to menu with this error. The issue is sporadic - their instance was working fine before, can suddenly get this, and then right after work again. Some people experience it every now and then, but otherwise can go many instance starts just fine in between.
The stacktrace includes com.sammy.malum.client.renderer.renderpass.ParallelWorldRenderer.<init>, however, both in the pack by default and confirmed for at least some of these occurrences their config/malum-client.toml has renderParallelWorld set to false.
Top of the crash written out here for easier searchability of this issue:
Description: Unexpected error
java.lang.IllegalArgumentException: Window 0x0 size out of bounds (max. size: 32768)
All reports are on pack version 1.5.0 and 1.6.0, both use Malum 1.8.2 - it's possible that's where the issue started, but can't be sure as crash assistant wasn't present in the pack much before that update so it's possible there were just no reports of it with Malum 1.8.1.
Couple collected reports of this crash (also excluding multiple reports by the same person):
StoneBlock 4 crashed. The logs have been uploaded to gnomebot.dev:
StoneBlock 4 crashed. The logs have been uploaded to gnomebot.dev:
StoneBlock 4 crashed. The logs have been uploaded to gnomebot.dev:
StoneBlock 4 crashed. The logs have been uploaded to gnomebot.dev:
Unfortunately don't have any specific context or reproduction of how this happens, but occasionally a report comes by of an FTB SB4 instance crashing on initial loading to menu with this error. The issue is sporadic - their instance was working fine before, can suddenly get this, and then right after work again. Some people experience it every now and then, but otherwise can go many instance starts just fine in between.
The stacktrace includes
com.sammy.malum.client.renderer.renderpass.ParallelWorldRenderer.<init>, however, both in the pack by default and confirmed for at least some of these occurrences theirconfig/malum-client.tomlhasrenderParallelWorldset tofalse.Top of the crash written out here for easier searchability of this issue:
All reports are on pack version 1.5.0 and 1.6.0, both use Malum 1.8.2 - it's possible that's where the issue started, but can't be sure as crash assistant wasn't present in the pack much before that update so it's possible there were just no reports of it with Malum 1.8.1.
Couple collected reports of this crash (also excluding multiple reports by the same person):
StoneBlock 4 crashed. The logs have been uploaded to
gnomebot.dev:latest.log | debug.log head / tail (~33k lines) | crash-2026-01-11_08.19.48-client.txt | KubeJS: client.log / startup.log | crash_assistant_app.log | modlist.txt
StoneBlock 4 crashed. The logs have been uploaded to
gnomebot.dev:latest.log | debug.log | crash-2026-01-11_13.19.40-client.txt | stderr_stream.log | KubeJS: client.log / startup.log | crash_assistant_app.log | modlist.txt
StoneBlock 4 crashed. The logs have been uploaded to
gnomebot.dev:latest.log | debug.log head / tail (~34k lines) | crash-2026-01-01_12.42.53-client.txt | PolyMC-0.log | KubeJS: client.log / startup.log | crash_assistant_app.log | win_event1767246180365.txt | modlist.txt
StoneBlock 4 crashed. The logs have been uploaded to
gnomebot.dev:latest.log | debug.log head / tail (~33k lines) | crash-2025-12-19_15.31.35-client.txt | stderr_stream.log | KubeJS: client.log / startup.log | crash_assistant_app.log | modlist.txt