Game run out of Memory even tho im using 64bit Version with 16GB of Ram

[TimiDeSuchti]

Ok so it keeps crashing randomly like every 30minutes or so, but only in Multiplayer... I Have no Idea why, it worked just fine i installed no new Mods or anything.

Current Mods: Calamity mod , Calamity mod Music, Wing Slot, Vein miner, Infinite ammo v1, Better Buffs, Boss Checklist, Recipe Browser, FKBoss health bar.

This is the log:


[13:01:52] [1/WARN] [tML]: Silently Caught Exception:
System.OutOfMemoryException: Array dimensions exceeded supported range.
at System.Collections.Generic.Dictionary`2.Initialize(Int32 capacity)
at System.Collections.Generic.Dictionary`2..ctor(Int32 capacity, IEqualityComparer`1 comparer)
at CalamityMod.CalPlayer.CalamityPlayer.HandleCooldownDictionary(BinaryReader reader) in CalamityMod\CalPlayer\CalamityPlayerNetcode.cs:line 326
at CalamityMod.CalamityNetcode.HandlePacket(Mod mod, BinaryReader reader, Int32 whoAmI) in CalamityMod\CalamityNetcode.cs:line 84
at Terraria.ModLoader.ModNet.HandleModPacket(BinaryReader reader, Int32 whoAmI, Int32 length)
at Terraria.MessageBuffer.GetData(Int32 start, Int32 length, Int32& messageType)
at Terraria.NetMessage.CheckBytes(Int32 bufferIndex)
at System.Threading.Tasks.Task.Execute()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot)
at System.Threading.Tasks.Task.ExecuteEntry(Boolean bPreventDoubleExecution)
at System.Threading.Tasks.ThreadPoolTaskScheduler.TryExecuteTaskInline(Task task, Boolean taskWasPreviouslyQueued)
at System.Threading.Tasks.TaskScheduler.TryRunInline(Task task, Boolean taskWasPreviouslyQueued)
at System.Threading.Tasks.Task.InternalRunSynchronously(TaskScheduler scheduler, Boolean waitForCompletion)
at Terraria.Netplay.OnUpdate()
at Terraria.Main.DoUpdate(GameTime gameTime)
at Terraria.Main.Update(GameTime gameTime)
at Microsoft.Xna.Framework.Game.Tick()
at Microsoft.Xna.Framework.SDL2_FNAPlatform.RunLoop(Game game)
at Microsoft.Xna.Framework.Game.Run()
at Terraria.Program.LaunchGame_()
at Terraria.Program.LaunchGame(String[] args, Boolean monoArgs)
at Terraria.FNALaunch.Main(String[] args)

[13:01:52] [1/FATAL] [tML]: Game ran out of memory. You'll have to find which mod is consuming lots of memory, and contact the devs or remove it.

[Inforcer]

Having the same issue. Running multiplayer anywhere from 20 minutes to 1 hour and game "runs out of memory." I have been running 32-bit or 64-bit and only the Calamity Mod (no other ones as they are all disabled to try to debug). Still same issue regardless of 32/64 version.

[dadeorion]

I've had the same issue here, no idea what causes it

[Inforcer]

Not sure if this will help or give clues, but here it goes. I tried to reinstall the 64-bit version and no luck. Still would randomly crash and give the memory error. An idea was shared that maybe after downloading the 64-bit version, a new map must be created and used to avoid the bug. Well to really test this and push the "memory error" issue, an extra-large map was made using the 64-bit version of TModLoader. There were NO ISSUES. We were able to play multiplayer/co-op via steam for hours without a crash. Our theory was it had to do with limitations placed on the map in a 32-bit mode vs and 64-bit mode. Give it a try and see if it works for you guys.

NOTE: From our experiment, a 32-bit client can play with someone on the 64-bit client. However, if the map is "extra large" the 32-bit client player will NOT be able to connect to the 64-bit client.

[Pierro]

Originally posted by Inforcer:

Not sure if this will help or give clues, but here it goes. I tried to reinstall the 64-bit version and no luck. Still would randomly crash and give the memory error. An idea was shared that maybe after downloading the 64-bit version, a new map must be created and used to avoid the bug. Well to really test this and push the "memory error" issue, an extra-large map was made using the 64-bit version of TModLoader. There were NO ISSUES. We were able to play multiplayer/co-op via steam for hours without a crash. Our theory was it had to do with limitations placed on the map in a 32-bit mode vs and 64-bit mode. Give it a try and see if it works for you guys.

NOTE: From our experiment, a 32-bit client can play with someone on the 64-bit client. However, if the map is "extra large" the 32-bit client player will NOT be able to connect to the 64-bit client.

i hope this isnt the only solution because ive only started having this issue myself after building a ton and getting to early hardmode

[Maclaudas]

Me and my bro been playing for the past 5 days with no issues, we even deleted mods to free up memory, no luck, still crashing. we've been playing for 4-5 hours straight, now cant even enjoy it for 30 mins.

[openbox]

Which ammo mod are you using exactly? The one I found is "infinite ammo" version 0.1, not 1.0 as you've listed. Perhaps you meant "Endless Ammo"?

[openbox]

I just tested your mod setup on my machine, and right now it seems that 64bit tModLoader has some deal-breaking performance issues. However, I can run the listed mods on 32bit tModLoader just fine without any problems, so I don't think you need the 64bit version. Last Friday there was an update to the 32bit version, so maybe 64bit version needs an update to match whatever changes were made.

[Nolan]

Newest calamity update makes it borderline impossible to play with friends ( Some of the code causes a memory leak and it absorbs all your ram ), you're gonna have to wait for 1.5.1.3 or you can downgrade to an older version

[epic]

Originally posted by Nolan:

Newest calamity update makes it borderline impossible to play with friends ( Some of the code causes a memory leak and it absorbs all your ram ), you're gonna have to wait for 1.5.1.3 or you can downgrade to an older version

source for this? Also, the calamity devs are aware of this issue right?

[Dr. Gregory House]

Hey there!

As confirmed by a previous poster, Calamity's most recent update (that being 1.5.1.2) currently has an issue where it will cause a detrimental memory leak. The team (as far as I am aware) is currently working on a fix.

The only solution that can fix this for now would be to downgrade to a previous version in order to avoid the leak entirely.

NOTE: This error is also known to cause drawcode-related crashes.

See you space cowboy,
~Ae

[TimiDeSuchti]

Originally posted by Æterna:

Hey there!

As confirmed by a previous poster, Calamity's most recent update (that being 1.5.1.2) currently has an issue where it will cause a detrimental memory leak. The team (as far as I am aware) is currently working on a fix.

The only solution that can fix this for now would be to downgrade to a previous version in order to avoid the leak entirely.

NOTE: This error is also known to cause drawcode-related crashes.

See you space cowboy,
~Ae

Oh okay thank you. Do you maybe know the latest version which doesn't crash?

[UnikornJezusOPC]

How do I downgrade to a previous version of Tmodloader?

[2024 ***** Winter Sale]

Originally posted by UnikornJezusOPC:

How do I downgrade to a previous version of Tmodloader?

There's no need. Also, make a new thread for off-topic questions.

[TimiDeSuchti]

Originally posted by Steviegt6:

Originally posted by UnikornJezusOPC:

How do I downgrade to a previous version of Tmodloader?

There's no need. Also, make a new thread for off-topic questions.

Why is there no need? did they fix it?

[Dr. Gregory House]

Originally posted by TimiDeSuchti:

Why is there no need? did they fix it?

This was said because this referred to downgrading tML, not Calamity, which was not mentioned anywhere in the discussion.