Transport Fever 2

Transport Fever 2

View Stats:
Juju83 Feb 12, 2023 @ 2:44pm
Out of Memory Error loading a saved game.
I'm getting an "Out of Memory" error saying
"There was an error allocating additional memory. If you repeatedly receive out of memory error message, please consider manually increasing the size of the page file."
I've already did that.
< >
Showing 1-15 of 15 comments
Metacritical Feb 12, 2023 @ 10:56pm 
the error is quite clear, what exactly are you asking us to do, tell you to play on smaller maps/use fewer mods until you buy more RAM?
Tsubame ⭐ Feb 13, 2023 @ 2:57am 
How much RAM and how much space did you manually allocate to page file?

The vanilla game, on your average map, is not too RAM hungry.

But larger maps with more development will use more memory. And more mods added to the savegame will also increase memory usage.
Juju83 Feb 13, 2023 @ 2:52pm 
Originally posted by Metacritical:
the error is quite clear, what exactly are you asking us to do, tell you to play on smaller maps/use fewer mods until you buy more RAM?

I have 32 gigs of ram. Page file is set to System Managed.. I think I have enough ram
Running RTX 2080
Intel i7 8700k
Corsair Dominator Platinum DDR4 @ 3200 Mhz.
Tsubame ⭐ Feb 13, 2023 @ 3:40pm 
How many mods and how large is the map being played?

I am assuming this only occurs on a specific map/save?

This game can easily top 30+ GB memory usage if you have hundreds of mods activated, and playing on very developed maps - i.e. lots of cities, vehicles, assets, and so on - on larger maps. So the 32 GB RAM may definitely be not enough, as the following screenshot on a save with 200 mods and 55k buildings or so shows:

https://steamcommunity.com/sharedfiles/filedetails/?id=2933165791

Windows sometimes have issues automatically quickly allocating the required page file. For a memory hungry game like this one, is better to allocate page file manually, to the highest amount possible. This will ensure you have the memory available at all times, and likely prevent further crashes. More details in this guide:

https://steamcommunity.com/sharedfiles/filedetails/?id=2760202773
Metacritical Feb 13, 2023 @ 11:40pm 
Originally posted by Juju83:
Originally posted by Metacritical:
the error is quite clear, what exactly are you asking us to do, tell you to play on smaller maps/use fewer mods until you buy more RAM?

I have 32 gigs of ram. Page file is set to System Managed.. I think I have enough ram
Running RTX 2080
Intel i7 8700k
Corsair Dominator Platinum DDR4 @ 3200 Mhz.
i also would have not included that useful information in the my first post either...

anyway, if you play on megalomaniac maps with lots of vehicle mods you might not still not have enough RAM.
Jorik Feb 14, 2023 @ 5:47am 
Originally posted by ᠌ ⁧⁧Tsubame ⭐:
How many mods and how large is the map being played?

I am assuming this only occurs on a specific map/save?

This game can easily top 30+ GB memory usage if you have hundreds of mods activated, and playing on very developed maps - i.e. lots of cities, vehicles, assets, and so on - on larger maps. So the 32 GB RAM may definitely be not enough, as the following screenshot on a save with 200 mods and 55k buildings or so shows:

https://steamcommunity.com/sharedfiles/filedetails/?id=2933165791

Windows sometimes have issues automatically quickly allocating the required page file. For a memory hungry game like this one, is better to allocate page file manually, to the highest amount possible. This will ensure you have the memory available at all times, and likely prevent further crashes. More details in this guide:

https://steamcommunity.com/sharedfiles/filedetails/?id=2760202773


I got 680 mods i play on Very Large (Megalomania) with over 100 villages and did not use 4 gigabyte of RAM but otherwise exceeded a bit on my VRAM.

Memory Out of Bound exception

One common indication of a memory leak is the OutOfMemoryError exception. Usually, this error is thrown when there is insufficient space to allocate an object in the memory heap. In this case, The garbage collector cannot make space available to accommodate a new object, and the heap cannot be expanded further. Also, this error may be thrown when there is insufficient native memory to support the loading of any class. In a rare instance, an OutOfMemoryError may be thrown when an excessive amount of time is being spent doing garbage collection and little memory is being freed.

When a OutOfMemoryError exception is thrown, a stack trace is also printed.



The OutOfMemoryError or Memory out of Bound exception can also be thrown by native library code when a native allocation cannot be satisfied.

An early step to diagnose an OutOfMemoryError exception is to determine the cause of the exception. Was it thrown because the heap is full, or because the native heap is full? To help you find the cause, the text of the exception includes a detail message at the end, as shown in the following exceptions.

-- Post your stdout.text and any .text. file you can find in userdata\301378565\1066780\local\crash_dump
yoshinoya Feb 14, 2023 @ 7:05am 
Originally posted by Metacritical:
the error is quite clear, what exactly are you asking us to do, tell you to play on smaller maps/use fewer mods until you buy more RAM?
I never got such an error until the latest beta update. I have 16GB of RAM and a manually defined 65GB pagefile. I don't get out of memory crashes on Cities Skylines with so many mods it would require 48+ GB of RAM to load it all... At least for me this crash happens when loading, so I think some mod or a bug in the update causes a memory leak.

In my stdout file there are dozens of lines containing "leaked:" before going Out of memory. Before all the "leaked:" lines is a "* Component TextView (class UI::TextView @ 0000029BBF5E2330)" so it's possible it has something to do with the UI change that made so many mods crash.


_CRASHDB_CRASH__ struct AssertException: C:\GitLab-Runner\builds\1BJoMpBZ\1\ug\urban_games\train_fever\src\Game\Application.cpp:682: void __cdecl `anonymous-namespace'::Run0(class UserProfile &,class platform::IPlatformBackend &,const class std::vector<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,class std::allocator<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > > > &): Assertion `false && "Out of memory"' failed.
Exception type: Fatal error

Details:

Assertion Failure: Assertion `false && "Out of memory"' failed.

Minidump: C:/Program Files (x86)/Steam/userdata/101441519/1066780/local/crash_dump/c96c0bdd-91ac-44eb-a915-0c2e6b66a299.dmp

In file: C:\GitLab-Runner\builds\1BJoMpBZ\1\ug\urban_games\train_fever\src\Game\Application.cpp:682

In function: void __cdecl `anonymous-namespace'::Run0(class UserProfile &,class platform::IPlatformBackend &,const class std::vector<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,class std::allocator<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > > > &)
Last edited by yoshinoya; Feb 14, 2023 @ 7:16am
Metacritical Feb 14, 2023 @ 7:22am 
Originally posted by sega rally championship:
Originally posted by Metacritical:
the error is quite clear, what exactly are you asking us to do, tell you to play on smaller maps/use fewer mods until you buy more RAM?
I never got such an error until the latest beta update.
the vehicles in the game have been upgraded with better models, these use more RAM for obvious reasons.
Mackintosh Feb 14, 2023 @ 8:22am 
I used to get these errors with a manually set swap file, but they disappeared when I went back to using the default, system managed setting. It seems they have inadvertently changed something again in the new beta that's causing this issue again. There's no reason anyone should be getting OOM errors on current hardware.
Metacritical Feb 14, 2023 @ 8:43am 
Originally posted by Mackintosh:
There's no reason anyone should be getting OOM errors on current hardware.
if you are only referring to unmodded games then i agree, assuming "current hardware" meets the system requirements of the game.
yoshinoya Feb 14, 2023 @ 9:22am 
Originally posted by Metacritical:
Originally posted by sega rally championship:
I never got such an error until the latest beta update.
the vehicles in the game have been upgraded with better models, these use more RAM for obvious reasons.
I don't use vanilla vehicles in the savegame I'm trying to load except those that cannot be disabled (buildings and AI cars).. I've noticed some models were changed at least according to their icons (BR 185 getting 4 pantographs), but that was before the latest update.

I don't know if I can trust Windows task manager when it comes to showing pagefile usage, but it looks like the game doesn't utilize the pagefile fully. When trying to load a game last time, it got to 100%, by which point the RAM + pagefile seemed to be about half full, and then it crashed with the Out of memory message.

Maybe it means out of VRAM, but that would still mean there is something wrong with the game, imo.
Morax Feb 14, 2023 @ 12:02pm 
A recent update to the test-version of this game broke some mods, which causes this error. Your memory is likely just fine!

In my case, just disabling the mod called "More Line Colours by LINX" fixed the issue:
https://steamcommunity.com/sharedfiles/filedetails/?id=1927330004
Juju83 Feb 14, 2023 @ 4:48pm 
Originally posted by Morax:
A recent update to the test-version of this game broke some mods, which causes this error. Your memory is likely just fine!

In my case, just disabling the mod called "More Line Colours by LINX" fixed the issue:
https://steamcommunity.com/sharedfiles/filedetails/?id=1927330004

Thanks. I did try to remove that mod and crashed the whole game lol.. Trying to disable it will CTD you with a huge window message with an error that comes with it.
Morax Feb 15, 2023 @ 11:40am 
You should disable the mod first from your save-file. From the main page, select Load Game, select Options (above the enabled mods-section on the right), scroll to the More Colors mod, click on the green box behind it to disable it, Apply Settings, and then try to load the game.
If that doesn't work or gives a CTD, reinstall the mod, and then try to disable it from the save first before removing it again.
Jorik Feb 16, 2023 @ 7:33am 
Please post your STDOUT.

I changed my Videocard today to a double video card but it was not crossfired yet. It booted the other card and i stumbled on the same error.

As following

Out of memory:
- size: 1027,1027
- render target: 0
- mip levels: 1
- layers: 1
- size: 2654208
- memory type: 15
- memory info:
* Host 390/7500
* VRAM 2374/2374
* VRAM 0/215
eatglobal: init [C:/Program Files (x86)/Steam/steamapps/workshop/content/1066780/2267827495/res/scripts/eatglobal_v2_29.lua] (Version 2.29)
eatglobal: init [C:/Program Files (x86)/Steam/steamapps/workshop/content/1066780/2026728411/res/scripts/eatglobal_v2_26.lua] (Version 2.26)
Attempting to write crash save to "crash_Noord-Holland Netherlands_2023-02-16_00-28-43"
eatglobal: init [C:/Program Files (x86)/Steam/userdata/301378565/1066780/local/mods/eat1963_roundhouse_fix_2/res/scripts/eatglobal_v2_25.lua] (Version 2.25)
available disk space: 341021 MB
[2023-02-16 00:28:43] Saving to file C:/Program Files
(x86)/Steam/userdata/301378565/1066780/local/save/savegame
Saving...: 42647.5 ms
Additional info extracted from the previous state:
Uncaught exception while in class UI::CSelector
[INFO: GENERAL]: 
- Objects 1:
Object 0: 0x227770019a0 of type Instance
Unloading layer library C:\WINDOWS\System32\DriverStore\FileRepository\u0375704.inf_amd64_9633b35ececb43fe\B367348\.\amdvlk64.dll
[INFO: GENERAL]: 
- Objects 1:
Object 0: 0x227770019a0 of type Instance
Unloading layer library C:\Program Files (x86)\Steam\.\SteamOverlayVulkanLayer64.dll
[INFO: GENERAL]: 
- Objects 1:
Object 0: 0x227770019a0 of type Instance
Unloading layer library C:\ProgramData\obs-studio-hook\.\graphics-hook64.dll
Exception type: Unknown exception

Details:

Error message: Out of video memory: ensure that you have enough video RAM and system RAM available. Consider lowering the texture quality.

Minidump: C:/Program Files (x86)/Steam/userdata/301378565/1066780/local/crash_dump/f7289c8d-40ea-4987-bc5b-3146b0e163a9.dmp

In file: C:\GitLab-Runner\builds\1BJoMpBZ\1\ug\urban_games\train_fever\src\Lib\renderer\vulkan\Image.cpp:88

In function: __cdecl vulkan_util::Image::Image(class VulkanRenderContext &,struct CVec2i,enum vk::Format,enum vk::SampleCountFlagBits,enum vk::ImageTiling,class vk::Flags<enum vk::ImageUsageFlagBits>,class vk::Flags<enum vk::MemoryPropertyFlagBits>,int,int,bool,bool,__int64 *)


__CRASHDB_CRASH__ struct Exception: C:\GitLab-Runner\builds\1BJoMpBZ\1\ug\urban_games\train_fever\src\Lib\renderer\vulkan\Image.cpp:88: __cdecl vulkan_util::Image::Image(class VulkanRenderContext &,struct CVec2i,enum vk::Format,enum vk::SampleCountFlagBits,enum vk::ImageTiling,class vk::Flags<enum vk::ImageUsageFlagBits>,class vk::Flags<enum vk::MemoryPropertyFlagBits>,int,int,bool,bool,__int64 *): Out of video memory: ensure that you have enough video RAM and system RAM available. Consider lowering the texture quality.

-------------------------------------------------------------------------------------

Second Attempt at running the Savegame

My Computer did something weird, switched cards.
-------------------------------------------------------------------------------------

Out of memory:
- size: 1024,1024
- render target: 0
- mip levels: 11
- layers: 1
- size: 1431552
- memory type: 15
- memory info:
* Host 482/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 1024,1024
- render target: 0
- mip levels: 11
- layers: 1
- size: 721920
- memory type: 15
- memory info:
* Host 482/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 1024,1024
- render target: 0
- mip levels: 11
- layers: 1
- size: 721920
- memory type: 15
- memory info:
* Host 482/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 1024,1024
- render target: 0
- mip levels: 11
- layers: 1
- size: 1431552
- memory type: 15
- memory info:
* Host 482/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 512,512
- render target: 0
- mip levels: 10
- layers: 1
- size: 370688
- memory type: 15
- memory info:
* Host 484/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 512,512
- render target: 0
- mip levels: 10
- layers: 1
- size: 370688
- memory type: 15
- memory info:
* Host 484/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 512,256
- render target: 0
- mip levels: 10
- layers: 1
- size: 180224
- memory type: 15
- memory info:
* Host 484/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 256,256
- render target: 0
- mip levels: 9
- layers: 1
- size: 92160
- memory type: 15
- memory info:
* Host 484/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 256,256
- render target: 0
- mip levels: 9
- layers: 1
- size: 46080
- memory type: 15
- memory info:
* Host 484/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 256,256
- render target: 0
- mip levels: 9
- layers: 1
- size: 92160
- memory type: 15
- memory info:
* Host 484/7500
* VRAM 2373/2373
* VRAM 0/215
Out of memory:
- size: 256,256
- render target: 0
- mip levels: 9
- layers: 1
- size: 46080
- memory type: 15
- memory info:
* Host 484/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 256,256
- render target: 0
- mip levels: 9
- layers: 1
- size: 46080
- memory type: 15
- memory info:
* Host 484/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 256,256
- render target: 0
- mip levels: 9
- layers: 1
- size: 92160
- memory type: 15
- memory info:
* Host 484/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 256,256
- render target: 0
- mip levels: 9
- layers: 1
- size: 46080
- memory type: 15
- memory info:
* Host 484/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 256,256
- render target: 0
- mip levels: 9
- layers: 1
- size: 46080
- memory type: 15
- memory info:
* Host 484/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 256,256
- render target: 0
- mip levels: 9
- layers: 1
- size: 92160
- memory type: 15
- memory info:
* Host 484/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 256,256
- render target: 0
- mip levels: 9
- layers: 1
- size: 46080
- memory type: 15
- memory info:
* Host 486/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 256,256
- render target: 0
- mip levels: 9
- layers: 1
- size: 46080
- memory type: 15
- memory info:
* Host 486/7500
* VRAM 2377/2377
* VRAM 0/216
Out of memory:
- size: 256,256
- render target: 0
- mip levels: 9
- layers: 1
- size: 92160
- memory type: 15
- memory info:
* Host 486/7500
* VRAM 2372/2372
* VRAM 0/215
Saving...: 45230.9 ms
Additional info extracted from the previous state:
Uncaught exception while in class UI::CSelector
[INFO: GENERAL]: 
- Objects 1:
Object 0: 0x22dac6bbb00 of type Instance
Unloading layer library C:\WINDOWS\System32\DriverStore\FileRepository\u0375704.inf_amd64_9633b35ececb43fe\B367348\.\amdvlk64.dll
[INFO: GENERAL]: 
- Objects 1:
Object 0: 0x22dac6bbb00 of type Instance
Unloading layer library C:\Program Files (x86)\Overwolf\0.218.0.8\.\owclient.dll
[INFO: GENERAL]: 
- Objects 1:
Object 0: 0x22dac6bbb00 of type Instance
Unloading layer library C:\Program Files (x86)\Overwolf\0.218.0.8\.\ow-graphics-vulkan.dll
[INFO: GENERAL]: 
- Objects 1:
Object 0: 0x22dac6bbb00 of type Instance
Unloading layer library C:\Program Files (x86)\Steam\.\SteamOverlayVulkanLayer64.dll
[INFO: GENERAL]: 
- Objects 1:
Object 0: 0x22dac6bbb00 of type Instance
Unloading layer library C:\ProgramData\obs-studio-hook\.\graphics-hook64.dll
Received SIGABRT
Heap corruption detected!
Calling thread crashtrace handlers
thread: 10796
(empty)

thread: 3032
(empty)

All thread handlers called
Minidump Callback
< >
Showing 1-15 of 15 comments
Per page: 1530 50

Date Posted: Feb 12, 2023 @ 2:44pm
Posts: 15