x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

Insane Memory Usage when copying, moving or renaming assets

OS: Windows 10 64bit (was: Windows 8.1 Pro 64-bit)
Version: Unreal Engine 4.11.2 (Launcher) (was: Unreal Editor 4.8.0 (4.8.0-0+++depot+UE4-Releases+4.8))

Description:
Certain Assets cause a seemingly infinite loop while opening them, rendering your system useless unless you act quickly enough. It will never progress further than loading the assets, most likely due to a circular reference somewhere.

Steps to reproduce:

  • Move, copy or rename assets.

  • Wait (some assets cause this, some don't)

  • Unreal Engine would now occasionally get stuck on loading, freezing in the process and start eating up all available memory.

Store Packages that produce this behaviour:
Use multiple to increase likeliness of it happening, one will rarely cause it directly, two most likely will and three are deadly.

  • SpaceBox_Color

  • SpaceBox_Variable

  • Open World Demo Collection

  • Infinity Blade packs

Product Version: UE 4.11
Tags:
more ▼

asked May 04 '15 at 08:56 PM in Bug Reports

avatar image

Xaymar
188 19 27 112

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

1 answer: sort voted first

Hi Xaymar,

When you modify assets in this manner, every asset has to be loaded into memory. The reason behind this and the additional time taken during this process is that the Editor must check references to all of those assets. If a link was broken when moving a material(for instance), ANYTHING that references that material would need to have it re-assigned manually.

Massive move operations require this to be done for EVERY asset. I would recommend setting aside some time for something like this in the future. This is especially true if you're using source control as well.

-Matt W.

more ▼

answered May 08 '15 at 02:35 PM

avatar image Xaymar May 08 '15 at 04:57 PM

Hello Williams,

that is an odd way to handle that then. What speaks against just creating a map of previous and new references and using that to modify the assets one by one, instead of all at the same time?

I tried to move the assets again by the way and Unreal Engine 4 ran out of memory. How exactly that happened is unclear to me, as the assets are only 440mb big.

avatar image Matt.Williams May 18 '15 at 09:29 PM

Hey Xaymar,

After some discussion with one of our engineers, I've gone ahead and entered UE-15795 with all of this information.

-Matt W.

avatar image Xaymar May 14 '16 at 12:31 PM

Issue is still there in 4.11, is anything ever going to be done about this? Manually moving Assets one by one is tedious especially because the launcher still does not offer an option as to where to place the assets.

Edit: And I'm not talking about many assets, it's usually just 4-5 assets that need to be moved. And those assets number ~400mb on disk, so how does Unreal Engine manage to eat up 64 gigabytes of RAM just to move those? Unity manages this just fine in under a second.

avatar image Xaymar May 17 '16 at 02:49 AM

Additionally now happen with deleting assets, but at least that one finishes before windows just closes Unreal Engine for using too much memory. I thought you guys fixed this...

avatar image Matt.Williams May 23 '16 at 03:31 PM

Hey Xaymar,

This issue is still listed as unresolved and isn't marked as high priority. Currently we don't have any other user reporting memory leak behavior like this and cannot reproduce it internally. The latter weighing heavily on a bug's priority.

The only thing that may help is to try to migrate your 4-5 assets to a blank project and reproduce it there. Note that this will bring with it all assets referenced by those 4-5. If you can reproduce it in the blank project with those assets, can you zip them up and send me a link to download it? You can PM me on the forums with a link.

-Matt W.

avatar image Xaymar May 23 '16 at 06:12 PM

Hey Matt,

my bad, I misread the 4.8 Known Issues as Solved Issues. Sorry. I've updated the question too, since we're using 4.11.2 now.

Anyway, it's reproducible using certain Store Packages I've found out, with the SpaceBox ones causing it almost 9 times out of 10. "Open World Demo Collection" causes this rarely (3 out of 10 times) and Infinity Blade packs cause it more frequently (4 out of 10 times). It seems that it gets more likely to happen the larger the individual asset is in it's raw form.

Anyway, I'll try to isolate the resources that cause it from the mess of resources and send them to you, given that it still happens when I isolate them.

  • Xaymar

avatar image Matt.Williams May 23 '16 at 07:04 PM

Thanks, let me know what you find as I'm trying this with open world and I can't seem to get it.

(comments are locked)
10|2000 characters needed characters left
Viewable by all users
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question