Migrating assets from 4.7.6 to 4.9.0 causes out of memory error
I am trying to migrate a project from 4.7.6 to 4.9.0 and I am encountering out of memory errors on packaged assets. It seems that any *.uasset I try to migrate will cause issues. I can migrate an asset from my 4.7.6 project to a new 4.7.6 project, but as soon as I try to migrate it to any other engine version, I get out of memory errors. I even had to hard reboot my computer.
I'm working with a source build of the engine and I made some slight modifications to ObjectVersion.h when I migrated my assets from 4.6.1 to 4.7.6 -- I think that these modifications permanently changed the package files during serialization and deserialization. I'd really like to just be able to migrate all of my content assets to the newest version of UE4.
To replicate this problem, I take a single asset from my 4.7.6 project and migrate it into the content folder of a brand new 4.9.0 project and then try to open the 4.9.0 test project. If you do this with the source build, you get this exception:
Ran out of memory allocating 18446744041135534544 bytes with alignment 0
If you run it off of a binary build, I think you'll just run out of memory and the computer will freeze because it tries to page it out to handle the impossible malloc request.
asked Sep 09 '15 at 04:29 AM in Bug Reports
It is possible that the edits to source code may have affected migration. Creating a blueprint in a 4.7.6 project and migrating it to a 4.9 project was successful for me including opening the 4.9 project after migration. Attempting to import your sample asset returns an error that it can't read the asset type (possibly related). Can you try creating an asset in a new 4.7.6 project and then migrate that asset to a new 4.9 project? If you're still getting out of memory errors you may need to revert the changes to your 4.7.6 source code or match the changes in your 4.9 source.
answered Sep 09 '15 at 06:07 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here