These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

Memory Leak ?
Author
Previous Topic Next Topic
Joseph North
Jolly Dodgers Rogering Codgers
Tactical Narcotics Team
#1 - 2016-02-08 00:00:15 UTC
Hi there,

For the past week or so EVE has been performing very weird with it's allocated memory. It starts out at 600-750mb memory, slowly climbing to upwards of 2GB memory used before dropping back down to 1gb and finally back down to 600 again. This is happening every few minutes, and often results in a 'EVE.exe has stopped responding' message which crashes the game.

It happens doubly for each new eve client that is ran.

Any insite into this would be fantastic. Hopefully I'm not the only person experiencing this.
Axhind
Eternity INC.
Goonswarm Federation
#2 - 2016-02-08 10:38:55 UTC
Joseph North wrote:
Hi there,

For the past week or so EVE has been performing very weird with it's allocated memory. It starts out at 600-750mb memory, slowly climbing to upwards of 2GB memory used before dropping back down to 1gb and finally back down to 600 again. This is happening every few minutes, and often results in a 'EVE.exe has stopped responding' message which crashes the game.

It happens doubly for each new eve client that is ran.

Any insite into this would be fantastic. Hopefully I'm not the only person experiencing this.

Are you using the new mumble overlay for directx11 by any chance?
Joseph North
Jolly Dodgers Rogering Codgers
Tactical Narcotics Team
#3 - 2016-02-08 11:17:54 UTC
I am actually, yeah. Does that have something to do with it?
Axhind
Eternity INC.
Goonswarm Federation
#4 - 2016-02-08 20:37:47 UTC
Joseph North wrote:
I am actually, yeah. Does that have something to do with it?


Yes. Mumble directx11 overlay has a memory leak. Easiest solution is just to turn on show FPS (the memory resets each time the overlay is actually triggered so if the channel you are in is very active it's not an issue).

I haven't tested the latest release but previously it would actually crush the client so perhaps they have managed to partially fix it.