We were using 4.10.4, and are trying to upgrade to 4.11.2. The project will convert and open fine the very first try, but if the editor is then closed and re-opened, even without changing/saving anything, it crashes on startup with the following error:
Access violation - code c0000005 (first/second chance not available)
I was able to locate all of the callstack reports for these crashes and I’ve created JIRA UE-31507 for the issue. Our developers will be investigating this further and we will post here with updates as we have them.
Unfortunately there’s not much to go on in the log. If you are still seeing this can you reproduce it in debug and gather some information?
It looks like it’s crashing in FTextureCubeResource::GetData() trying to init some cubemap.
When it crashes could you gather some data on which face is being mapped, which mip, the src/dest pitch. The Destination and src pointers for the memcopy that appears to be crashing.
Also if you can go up the callstack to the FTextureCubeResource see if you can identify which cubmap it is via the Owner member variable. This might give us a clue if you have some corrupted asset.
I poked around in the Owner but wasn’t able to find anything that I was able to use to identify the asset, anything relating to filenames or source was either empty or not a value I could translate to a specific asset. Can you give me an idea of what I can look for?
Just some additional info on the crash itself:
It seems to only happen the first time an asset is opened after opening the editor, but not always. Doesn’t seem to matter what asset, I can choose one at random (map, blueprint, etc) and it’ll crash. If I then re-open the editor and try to open that same asset that crashed it previously, it’ll crash nearly 100% of the time. But if I instead choose a different asset randomly, it’s more likely to open without crashing, then opening that previous asset will be fine. And once it does open an asset successfully, it’ll usually be fine for the duration of that session.
That’s great info. We’ll update our internal tests to see if we can get a repro with this texture and find out what happened. Thanks for reporting back.
It was mostly luck that we found it. But I believe we noticed that the thumbnail for one of the texture cubes looked all garbled while browsing in the editor.
To be clear, my issue does not involve a converted project, but a project that was born (and still is) in UE 4.12.5.
Basically, the packaged application reports the above mentioned problem at start and crashes. I solved it by simply migrating my map to an empty project, although the solution was temporary; after a few hours of work, it manifested again, and I had to re-migrate my map to yet another project.
Go figure …