Ошибка террарии game ran out of memory

Description

Whenever I tried to switch outside of tml using win+tab then switch back, the screen becomes white and the program itself stops responding, then there’s the error message «Game ran out of memory. You’ll have to find which mod is consuming lots of memory, and contact the devs or remove it.» This happens randomly when using win+tab, by that I mean sometimes it works fine but sometimes it crashes.
I do have a lot of mods installed/enabled, this includes: calamity (mod+music), thorium, luiafk, alchemistnpc (not lite), cheat sheet and veinminer.
My pc’s display is 3840×2160 and I run the game at 1920×1080
I have an extra memory chip installed so the total memory is 32GB, there’s no way a 2D pixel game can use up to 32 gb of ram, and the task manager proves it.
However, there’s an issue, the window resizes a few times before entering fullscreen. I’ve learned this from the following log messages:
«[13:22:42] [1/DEBUG] [Terraria]: Device Reset, Profile: HiDef, Width: 800 -> 1280, Height: 480 -> 720, Fullscreen: False -> True, Display: .DISPLAY1
[13:22:43] [1/DEBUG] [Terraria]: Device Reset, Profile: HiDef, Width: 1280 -> 1920, Height: 720 -> 1080, Fullscreen: True, Display: .DISPLAY1
[13:22:44] [1/DEBUG] [Terraria]: Device Reset, Profile: HiDef, Width: 1920, Height: 1080, Fullscreen: True, Display: .DISPLAY1″
These are always in the log file and the effect is noticeable too.

Does this affect it? Because I’m pretty sure it’s related.

I’m pretty sure it’s the game because this only happens when using win+tab. In some cases, this always happens when using win+tab. That means it never happens in-game, so it’s not actually the game running out of the memory, more like a bug which happens when resizing the window.

Log file

Client is completely normal, until:

[13:36:05] [1/DEBUG] [Terraria]: Device Reset, Profile: HiDef, Width: 1920, Height: 1080, Fullscreen: True, Display: .DISPLAY1
[13:36:06] [1/WARN] [tML]: Silently Caught Exception:
System.OutOfMemoryException: Insufficient memory to continue the execution of the program.
at Microsoft.Xna.Framework.Helpers.GetExceptionFromResult(UInt32 result)
at Microsoft.Xna.Framework.Graphics.GraphicsHelpers.GetExceptionFromResult(UInt32 result)
at Microsoft.Xna.Framework.Graphics.RenderTargetHelper.CreateSurfaces(GraphicsDevice graphicsDevice)
at Microsoft.Xna.Framework.Graphics.RenderTarget2D.RecreateAndPopulateObject()
at Microsoft.Xna.Framework.Graphics.DeviceResourceManager.RecreateResources(D3DPOOL pool, Boolean deviceRecreated)
at Microsoft.Xna.Framework.Graphics.GraphicsDevice.Reset(PresentationParameters presentationParameters, GraphicsAdapter graphicsAdapter)
at Microsoft.Xna.Framework.GraphicsDeviceManager.ChangeDevice(Boolean forceCreate)
at Microsoft.Xna.Framework.GraphicsDeviceManager.EnsureDevicePlatform()
at Microsoft.Xna.Framework.GraphicsDeviceManager.Microsoft.Xna.Framework.IGraphicsDeviceManager.BeginDraw()
at Microsoft.Xna.Framework.Game.BeginDraw()
at Microsoft.Xna.Framework.Game.DrawFrame()
at Microsoft.Xna.Framework.Game.Paint(Object sender, EventArgs e)
at Microsoft.Xna.Framework.GameWindow.OnPaint()
at Microsoft.Xna.Framework.WindowsGameWindow.mainForm_Paint(Object sender, PaintEventArgs e)
at System.Windows.Forms.Control.OnPaint(PaintEventArgs e)
at System.Windows.Forms.Form.OnPaint(PaintEventArgs e)
at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at Microsoft.Xna.Framework.WindowsGameForm.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at Microsoft.Xna.Framework.Input.UnsafeNativeMethods.CallWindowProc(IntPtr lpPrevWndFunc, IntPtr hWnd, UInt32 msg, IntPtr wParam, IntPtr lParam)
at Microsoft.Xna.Framework.Input.WindowMessageHooker.Hook.WndProc(IntPtr msgWnd, UInt32 msg, IntPtr wParam, IntPtr lParam)
at ReLogic.OS.Windows.WindowsApi.CallWindowProc(IntPtr lpPrevWndFunc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at ReLogic.OS.Windows.WindowsMessageHook.WndProc(IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at Microsoft.Xna.Framework.WindowsGameHost.Run()
at Microsoft.Xna.Framework.Game.RunGame(Boolean useBlockingRun)
at Terraria.Program.LaunchGame()
at Terraria.Program.LaunchGame(String[] args, Boolean monoArgs)
at Terraria.WindowsLaunch.Main(String[] args)

[13:36:06] [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.

And then the error pops up

Steps to reproduce

Using win+tab to swtich between the game and other tabs opened. Then switch back into the game.

Expected behavior

It was normal before, the window still resizes before entering full screen and I can use win+tab whenever I want, even in multiplayer. It’s just after the most recent update, this issue keeps occuring.

Actual behavior

crash

Reproduction frequency

Sometimes it’s guaranteed , sometimes it doesn’t crash at all.

Additional Information

No, it just happens all the time.

Lastly, I do wanna know if it’s actually my pc and do I have to update my drivers.

edit: this also happens when i accidentally press the win key (only the win key nothing else)

and it seems that when the error pops up the game’s resolution is at like 800×600 or something

There is a bit of trouble when you try to run mods in Terraria. The game was made to run on its own and with the amazing work of the community, there are tons of content to be consumed including some quality of life improvements that only mods can do.

Running too many of these mods can cause Terraria to crash especially with texture changes.

There are mods like the “Legend of Zelda” or “Dragon Ball Terraria” that make the game run more things that were not accounted for by the developers. On some occasions, this will cause your game to crash.

Terraria is a bit (pun intended) different when it comes to allocating more RAM to a Steam game which will all be explained below.

This guide will teach you how to allocate more RAM to Terraria and run all the mods you can without crashing as long as they are compatible.

Explaining RAM or Memory Usage in Terraria

Just by the look of the game and how it is played, it should be easy to run for almost any RAM installed on your computer. Terraria is a 2D sandbox game that is quite similar to the old platformer games in the ’90s.

In short, Terraria should not take much of your total memory capacity. The game runs in 32-bit which means that the total memory that can be used for the game will be at 4GB.

With so many things going on at the same time, the game should still run perfectly fine. Even if you have a big base with automated switches for farming while being attacked by the Destroyer with 3 other friends (all happening on the same screen), it should still run fine.

In my personal experience, the only time you would need more RAM allocation for Terraria is when you have installed mods made by the community to add some quality of life features or adding more entertaining content to spice up your world.

Installing tModLoader 64-bit Through Steam

The tModLoader has already been implemented in the additional content side of Terraria. You can search for it in the Steam’s store and you will be able to download it for free if you have Terraria on Steam.

Download all the mods you want to load and make sure you are using tModLoader. It is basically the game’s mod manager to make things easier.

After finishing downloading and installing, you still need to do another download which is the 64-bit “mod” that you need to run with tModLoader.

How to Make Terraria Use More RAM

As previously mentioned, Terraria is a 32-bit game. That means the total memory used for the game will be maxed out at 4GB. That means If you go anywhere above 4GB, Terraria will run out of memory and crash.

The first step to give Terraria more RAM so you can use all the mods you want in the game is to modify your Terraria file to a 64-bit version. There is a simple way to do this and you will need to make a few installations and a folder to drag inside your installed Terraria folder.

Download the 64-bit tModLoader from the forums page and choose the appropriate (latest) version for your current Terraria version. Unzip the file “tML 64 (current Terraria version)” and choose a destination for the folder inside.

Open your tModLoader folder by looking through your installed Steam library folder. You can find it by going through Steam > steamapps > common > tModLoader.

If you are having trouble finding it, you can right-click the tModLoader directly in your Steam library. After right-clicking, go to manage and choose “browse local files”. This should open your tModLoader folder (it is worth noting that this is not your Terraria folder).

After opening the tModLoader folder, drag all the files from the unzipped file (64-bit tModLoader you downloaded from the forums) and paste it inside. You need to choose “replace all files” and finish the copy.

To check if it is working, you can open your tModLoader (not the Terraria game) to launch Terraria. It will open up a command prompt but you just need to wait for it to load everything.

Once it opens Terraria and starts loading your mods, you will see on the lower-left corner that it is running in 64-bit. It should look something like the picture above.

Conclusion

Once you are running the 64-bit version of Terraria, you should be able to give Terraria more memory to run as many mods as you can (of course, they have to be compatible with each other).

They have thousands of mods created by the community and it breathes new life into the game if you have already finished the standard version.

You can also account for hosting the server with your friends because you will need more RAM for hosting. The same concept goes in knowing how to allocate more RAM to a Minecraft server.

This is why changing Terraria to 64-bit is a must when you need to allocate more RAM to Terraria. Just remember that you need to wait for updates constantly for the tModLoader if ever Terraria updates their game again. Otherwise, you’re likely to experience tModLoader memory crash issues.