Crash on Editor Startup: Failed to uncompress memory

LogCompression:Error: FCompression::UncompressMemory - Failed to uncompress memory (129344/131072), this may indicate the asset is corrupt!

Working in material editor when all of the sudden I’m getting shader errors without making any changes. Save project and try to reopen and I find that not only am I unable to open this project, but every single of one of my previously saved backups (this project only) also will not open.

The only thing the error logs have in common is this failed to uncompress memory error. Can anyone help?

I have already tried deleting all .ini files and the DDC folder and I just finished a complete reinstall of UE4. link text

Hello SVR33,

It looks as if you are running out of memory.

1.) On what drive are you saving your projects?
2.) Can you create another drive and save it to another drive with more allocated memory space?
3.) Can you link your DXDiag?

After you troubleshoot some of these steps comment again and I will see if I can narrow down whats causing this issue.

Thanks,

Hi ,

Thanks for the response. Just a few weeks ago, I moved moved my primary project files over to a 120 GB SSD which contains only that project (something I did in the hopes of speeding up my editor load times). Those files are only using ~5GB of the drive, so it has plenty of free space. Every few days I make a copy of this project folder and put it in a ‘backup’ folder on my C drive (which is currently using ~800GB of its 1TB drive capacity). When my main project first started giving me this error, I tried opening previous backup files and they, also, failed to open with the same error. Next step, I completely uninstalled UE4 and reinstalled it onto the SSD (as opposed to the C drive, where it was) but I still had the same problem. After fighting with that for a day, I posted this question.

The next day, FINALLY, I was able to get one of my project backups from January to actually open in the editor - this took somewhere between ‘countless’ and ‘infinite’ attempts in desperation. Then, after that, I was able to open a backup from February… then March… all the way up to my backup from just a few days ago and, now, even the current project file (on the SSD) opens up again without issue.

My gut tells me you are correct… it does seem to be memory related, as each of these backup files grows in size each month, but I have 32GB of RAM and plenty of drive space… this shouldn’t be an issue. While I am able to open my project again, the editor feels very sluggish and I’m afraid this might happen again. Any thoughts as to what might be going on here?

Thanks

DxDiag attached

Hey SVR33,

Good idea making the backups.

What I would do is run your editor without your project. Just load a project with starter content, and open up the minimal default level, loaded upon opening a new project.

I would then do a system performance check through your Task manager and take a look at the CPU Usage and memory.

If this is spiking when playing the editor alone then you may have to move all of your projects, if you have any others, to your alternate drive to free some space.

If it doesn’t spike then this could be an issue involving your project specifically.

Let me know what you find out.

Thanks,

Hello SVR33,

I am checking to see if you were able to get the same issue with a fresh project?

Thanks,

Hi ,

I only had a short moment yesterday to test this and I’ll do a proper set of tests tonight but when opening a new fresh project with only starter content, memory usage never went abover 4GB and opened very quickly with no issue. I then tried opening my main project with the Windows performance monitor open and what I saw happening is that RAM, surprisingly, never went above 5GB (of 32GB) but my CPU was spiking to 100% and the editor crashed when the loading screen got into the ~90% range. This wasn’t the standard editor crash with a log dump but instead the windows “unreal engine has unexpected shut down/is not responding”, which is the first time this has happened. I will report back after trying again tonight.

Hi SVR33 -

Your DXDIAG shows you are running an older version of your Video Cards Driver. Can you please update to the most current version of the Nvidia Driver, 355.60, and see if the issue resolves once updated? If not please post back here and let us know.

Thank You

Eric Ketchum

Hi Eric,

I actually tried rolling back my drivers as a solution when this problem first showed up. I was using the most recent Nvidia drivers before this crash started and simply haven’t re-updated. Since my last message, I’ve only had one time that I was unable to open the project. I went and deleted the Boot.ddc file and all has been well, since then.

I still get the feeling these crashes are being initially triggered by hardware issues and I’ve gone from believing that the hard drive, CPU, RAM and motherboard were each responsible, at some point. Now, I have no idea what’s really doing it. HD/SSD and RAM tests all come back clean. Odds are I will just have to bite the bullet and build a new machine from scratch to escape these gremlins.

Also have a look at secondary software (my term) software that is monitoring your CPU or GPU, it is not often but they too can have some effect.

I am going to accept the answer above, resolving the issue, but should you need further help please feel free to comment below and we will get back to you.

Thank You

Eric Ketchum