World Composition - Filling layer information causing huge memory usage / memory leak?

Hey!

First of all im not sure it is bug or not, but seems kinda like a bug or memory leak.

Situation:

  • I created a brand new project
  • Made a new tiled heightmap in World Machine with layer informations (like beach, mountains etc.)
  • Imported as tiled landscape
  • Created our landscape material
  • Made new layer informations for every layer
  • Tried to import Layer information from file.

And this is where things goes weird…

My PC is quite not a big one, but here is the specs: I7 8700k, 16 gb ddr4 , r7 360 2gb

First i noticed engine crash after a few mins with “out of video memory” window…
Okay… i know 16 gb memory is not a lot, so i tried to increase virtual memory and import again…

Same thing happened… so i decided to run a few test…

In my last test Virtual memory size was manually entered by me and was 144 GB

Guess what happened next…

After layer information import Engine started to build textures for landscape (based on log engine did their job)
Engine slowly consumed all of the RAM and crashed…

After engine crash memory usage was still high and pagefile was not cleared btw.

Dont know if this is normal, but in the log i saw lot of repeat.

[2018.08.31-10.35.51:069][496]LogTexture: Display: Building textures: Texture2D_4 (BGRA8, 128X128)
[2018.08.31-10.36.10:326][496]LogTexture: Display: Building textures: Texture2D_5 (BGRA8, 128X128)
[2018.08.31-10.36.15:845][496]LogTexture: Display: Building textures: Texture2D_6 (BGRA8, 128X128)
[2018.08.31-10.36.20:976][496]LogTexture: Display: Building textures: Texture2D_7 (BGRA8, 128X128)
[2018.08.31-10.36.26:385][496]LogTexture: Display: Building textures: Texture2D_8 (BGRA8, 128X128)
[2018.08.31-10.36.31:860][496]LogTexture: Display: Building textures: Texture2D_9 (BGRA8, 128X128)
[2018.08.31-10.36.37:018][496]LogTexture: Display: Building textures: Texture2D_10 (BGRA8, 128X128)
[2018.08.31-10.36.47:762][496]LogTexture: Display: Building textures: Texture2D_11 (BGRA8, 128X128)
[2018.08.31-10.36.55:166][496]LogTexture: Display: Building textures: Texture2D_4 (BGRA8, 128X128)
[2018.08.31-10.37.11:733][496]LogTexture: Display: Building textures: Texture2D_5 (BGRA8, 128X128)
[2018.08.31-10.37.17:909][496]LogTexture: Display: Building textures: Texture2D_6 (BGRA8, 128X128)
[2018.08.31-10.37.25:758][496]LogTexture: Display: Building textures: Texture2D_7 (BGRA8, 128X128)
[2018.08.31-10.37.31:114][496]LogTexture: Display: Building textures: Texture2D_8 (BGRA8, 128X128)
[2018.08.31-10.37.36:945][496]LogTexture: Display: Building textures: Texture2D_9 (BGRA8, 128X128)
[2018.08.31-10.37.42:173][496]LogTexture: Display: Building textures: Texture2D_10 (BGRA8, 128X128)
[2018.08.31-10.37.49:022][496]LogTexture: Display: Building textures: Texture2D_11 (BGRA8, 128X128)
[2018.08.31-10.37.55:176][496]LogTexture: Display: Building textures: Texture2D_4 (BGRA8, 128X128)
[2018.08.31-10.38.17:238][496]LogTexture: Display: Building textures: Texture2D_5 (BGRA8, 128X128)
[2018.08.31-10.38.24:084][496]LogTexture: Display: Building textures: Texture2D_6 (BGRA8, 128X128)
[2018.08.31-10.38.29:294][496]LogTexture: Display: Building textures: Texture2D_7 (BGRA8, 128X128)
[2018.08.31-10.38.36:855][496]LogTexture: Display: Building textures: Texture2D_8 (BGRA8, 128X128)
[2018.08.31-10.38.44:504][496]LogTexture: Display: Building textures: Texture2D_9 (BGRA8, 128X128)

Is this normal thing? Engine built Texture2D_4 124 times. [Full Log][4]
Im not sure this supposed to work in this way. Correct me if im wrong, but…
okay 16 gb memory is not much (Also just sidenote: we tried on another PC with 64 gb memory and crash happened there too), but 144 gb virtual memory should be enough even if slower as the dedicated memory…

or is there any problem with using virtual memory? UE4 is not able to use pagefile properly? maybe things goes wrong when windows write memory to disk?

Can any UE4 developer hop in and explain whats happening and how we can fill layer informations if engine crash with 16 gb memory, 64 gb memory… should we buy more ram? :slight_smile:

Hello,

We’ve recently made a switch to a new bug reporting method using a more structured form. Please visit the link below for more details and report the issue using the new Bug Submission Form. Feel free to continue to use this thread for community discussion around the issue.

https://epicsupport.force.com/unrealengine/s/

Thanks

I too just rebooted my engine because I noticed it taking up 10gigs in memory with no levels loaded! I had just been doing fill all on a series of tiled levels.

I also encountered this problem and asked for help.

Dont worry guys.

This is now a confirmed issue:

Epic doing great job and hopefully will be fixed once :slight_smile: