Massive bug in Epic Games Launcher VRAM Usage

It has been a month since i noticed it and i can’t believe nobody have reported it yet, since a month or so(it might be more) the epic games launcher started using 4Gb of VRAM after launch, NOT system RAM, VIDEO RAM, GPU RAM, whatever you want to call it, the dedicated memory storage for the graphics card.

I have tested it on my Tower pc, an old laptop and my new laptop and also a completely fresh install of windows with just drivers and the Launcher, ALL present the same issue, after opening the launcher it just starts eating the VRAM, and does not even respect the iGPU vs dGPU priorities, all my other programs go to the iGPU shared memory, but the Epic Games Launcher goes DIRECTLY to dGPU VRAM, it goes from 0 to 4Gb by ONLY opening the launcher.

After some investigations and tests i have discovered that it happens on logged in accounts, if i SignOut it frees most of the VRAM(still uses around 300-500Mb of VRAM just in the login screen), and if i login again it starts to eat the VRAM for breakfast again…

Task Manager “Details” tab after fully loaded Launcher
Screenshot_1

Task Manager “GPU” tab after fully loaded Launcher

After Signing Out with Launcher open but at the Login Screen

After Logging in again

Hi there,

Thanks for letting us know about this issue. I have passed it along to our development team for an internal review.

2 Likes

Same for me, not 4GB but plenty

Same problem here I get 3 Gb of VRAM Use from Epic Launcher, even running in the background, any fixes Yet ?
I have Rx 6600 XT 8 Gb on Windows 10

God 4gb it’s insane! I have 2.5gb use.

Any news on this? It’s still there, how are we supposed to play games when up to 90% of the video memory is already used for just the launcher… 8Gb(in my case) is already on the limit of not being enough, slicing that in half has BIG impact on performance, makes play any games on EGL a very bad experience…

When i reported the bug it was already happening for like a month or two(since i noticed), how is that an so impactful problem like this not receiving any attention for such of a long time?

It hasn’t been updated for a month.

Hello all,

Thank you all for reporting this issue and your experience! I’ve made the appropriate teams aware of this issue and we’re actively investigating this. We consider this a high priority issue, so expect an update on this in the near future!

If you haven’t performed any troubleshooting, I recommend starting with this article. These steps could alleviate some of your issues while we investigate, so I encourage you to try them if you haven’t already.

Look forward to receiving an update on this!