Sodium Reloaded (Unofficial)

Sodium Reloaded (Unofficial)

Mods
0 Downloads

Random crashes

INotSleep opened this issue ยท 2 comments

commented

Version information

1.19.3 0.4.6.build20

Reproduction Steps

  1. Open minecraft
  2. Play 20 mins - 2-3 hours
  3. Get crash

Crash Report file

There no crash report, but there log and hserr log
hs_err_pid16756.log
2023-02-21-4.log

Additional information

No response

commented

Update Sodium, you're most probably experiencing the NVIDIA driver crash, which Sodium has a workaround for since 0.4.7.

commented

You ran out of memory. Sodium can be seen panicking in the logs trying to reclaim memory:

[19:49:03] [Render thread/WARN]: Reclaimed 3840 bytes at address 2531164880896 that were leaked from an unknown location (logging is disabled)
[19:49:03] [Render thread/WARN]: Reclaimed 94240 bytes at address 2526282386304 that were leaked from an unknown location (logging is disabled)
[19:49:03] [Render thread/WARN]: Reclaimed 288 bytes at address 2282878406080 that were leaked from an unknown location (logging is disabled)
[19:49:03] [Render thread/WARN]: Reclaimed 33280 bytes at address 2530211990720 that were leaked from an unknown location (logging is disabled)
[19:49:14] [Chunk Render Task Executor #2/ERROR]: EMERGENCY: Tried to allocate 21520 bytes but the allocator reports failure
[19:49:14] [Chunk Render Task Executor #2/ERROR]: EMERGENCY: ... Attempting to force a garbage collection cycle (attempt 1/3)

At which point the JVM crashes...

#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 1048576 bytes for AllocateHeap
# Possible reasons:
#   The system is out of physical RAM or swap space

Sodium 0.4.7 fixed a memory leak that was rather severe, but you are using Sodium 0.4.6. I suspect if you update the mod that your problem will be fixed.