4.8 Massive performance drop

After I updated from 4.7.6 to 4.8 Unreal started using over 12GB out of total 16GB of RAM without carrying out any kind of rendering or process, just opened Unreal 4.8 and the RAM meter hit the skies, when playing in editor window FPS drops from 120 in 4.7.6 to less than 20 down to 5 in 4.8
Any solution? My work is completely frozen!

The same issue for me. Before it was about 60 fps on gtx 560 ti now… 3 maybe 4 fps ^^ I heard something about metal draw bug or smoething similar, have you got many “metal” surfaces and materials?

Not even a single metal shrapnel :smiley:

I have done some test (becouse i have noticed only one of our levels have got 3 fps - rest of them is working normal). I have moved all static meshes to new level and it was much better. I have deleted all postprocess, reflection captures and particle emmiters. Hm. I remember we have similar issue in 4.3 / 4.4 with reflection captures.

So many time wasted. Time to back to 4.7.4 :x

Hi all,

Would you mind checking your output log for any log spam?

When your memory gets out of control again, let it grow as high as you feel comfortable with. Then bring up the console with ~ and enter memreport -full. Rename the extentions on the .memreport file to .txt in the [ProjectName]/saved/Profiling/MemReports folder and then attach it here.

Can you also attach your dxdiag info?

@anonymous_user_b40ad815: We’ve been trying to track down the cause of a memory leak for a while now, but have not been able to reproduce locally. Appears it could be a strange combination of some rendering feature and certain hardware. We haven’t really gotten anybody that gets this issue to help us narrow it down with some testing on their end. Would you be willing to go through that level and disable post processing features one at a time? I don’t know if you’d need to restart the editor after each one to get the memory to go down though.

-.

Hm… it may be little hard to do… becouse after few sec with 3 fps it is imposibble to do anything, - just restart :stuck_out_tongue:

Dont worry. I will wait for next version :slight_smile:

That’s your decision, but we can’t fix a problem we can’t reproduce or get info from our users about. I can’t guarantee it’ll be fixed in the next build.

I have been trying to track the error cause, no luck with the post process though, however, it might be a rendering mobility between major two versions of the engine? since I remade the level and everything is normal as far as I’ve gone remaking…
I will keep digging while working

Hey Quwatli,

Thanks for checking back in. I’m glad it’s working alright after remaking the level. It’s annoying that conversion issues like this are there, but it happens during active engine development. Let me know if you run into anymore conversion issues.

-.