Issues, Workarounds & Localization

The memory leak for me was related to audio.

If I had audio enabled in EVE the memory usage consistently increased to well over 2Gb before I ended up having to restart due to stuttering and lag. Disabling audio in the client prevented the leak and the memory seems to top out at around 600Mb at most after a lot of in-space activity (missions or whatever) but drops below this after periods of inactivity in station, which it never did with the audio enabled.

Heck, with audio enabled I could sit in station and the memory footprint would just escalate seemingly infinitely.

So, back to 'EVE has sound?' for me at least heh.

Aha, that's why it seemed familiar when I wrote that post lol. Sorry, my memory is terrible these days and since I hardly ever touch the forums I'd forgotten you'd already tried it.

Tbh, the memory usage is pretty schizophrenic even without a memory leak nowadays. One of my clients can start with as little as 300Mb at log on, but another with the same settings and in the same system uses 480Mb+ straight away before even undocking or opening the skill queue, and it's not even consistent as to which uses more.

I really hope you can figure this out and that CCP fixes it soon.

Ever since two patches ago, I am now unable to run 3 clients. It is choppy, and pauses a lot. While running just two I still get pauses, and lockups, just not a frequent. Everything can slow down to a crawl, but can come good by either hitting ESC on both clients, and then returning to the play screen, or just wait for everything to unfreeze itself which can take up to a minute. I do not run audio at all.

I ran the memory diag tool for Win7 64, and it came back with zero errors, but running the resource monitor in the background reveals major page file, or as it's now called, 'Hard Faults' spikes up to 100. With 1 client they hardly appear. I have an 8Gig set page file size, and am running 6Gig of RAM.

Please help CCP, as this is making it quite unplayable, especially during wars.

Having played since early 2005, why does this answer come as no surprise.... EXODUS RMR had the same issues and we got the same answers. SImply put CCP does not like smart gamers, they want dumbass theme park gamers who won't bother them with difficult questions. Why anyone who plays EVE thinks this attitude will ever change beats me, just play the game, restart clients/flush cache and don't bother complaining cause that's as far as it will go.

Confirming some kind of memory leak / cache error, and even today Windows 7 gave me this warning message.

Error message :
http://i.imgur.com/szNj6.png

Details :
http://i.imgur.com/uc0JD.png

I have an i920/2.66Ghz w/ 12GB DDR3 memory and 2 x Nvidia GTX480/1.5GB memory and Windows 7/64Bit

3 Clients was at respectively (when Windows popped up the error message)
- 2.46 GB
- 1.34 GB
- 1.10 GB

It seems like the memory keeps counting up at a rather slow pace, but peaks after a few hours which may cause erratic instability and crashes, at least this is how I've perceived it.

My best guess is that the eve client have one or more conditional memory leaks, but I'm not paid to find out which :)

Cheers, good luck fixing this.

I am currently running 5 eve clients with no real problems. I also read the forums and control my brothers computer through teamviewer and have evemon running all at once. It's been running since 9:30am mtn and the most they are taking up is about 850mb each. No real performance issues really. I use the optimize settings memory and, they are going without a hitch.

Now, I do have a 6 core proc, 8gb of ram, and a 4870x2 in my system too all on win7 64bit.

So, are you saying it was b/c you had "show effects" ON, and now have it off? B/c if so, if "show effects" is causing this ram leak, as much as it pains me, i don't think i would enjoy playing an internet spaceship games with "effects" turned off....or am i wrong?

I'm still seeing this leak.

It is sporatic at this stage, one day it might only climb 200mb, another day it will climb more than that, all while doing the same activity (mining) for roughly the same amount of time.

Bump. And Robert, it is not the fault of the card manufacturers when this only happens with EVE. CCP needs to figure this out and fix it. If only because it is hurting them and going to hurt them more in the pocket book.

edit - And I wonder whether it is eve-voice related. I have a desktop that can't seem to run eve anymore without continuous freezeups. Meanwhile a laptop that is not experiencing the problems. I have never used eve-voice on the lappy. I did on the desktop. I have since disabled sound on the desktop. But from reading this thread i wonder whether it has not turned off somehow.

When doing station trading, the Eve client gets slower and slower as time goes on.

For example, you log in. The trade dialog boxes are kinda fast.

24 hours later, the client has probably degraded so much that most times you pull up buy/sell/modify: First a window appears with some empty grey area, then it lags, then it resizes, then the numbers appear, then the I-beam cursor quickly flashes to catch up all the ticks it should have been ticking for, and you can finally reliably type something in.

Restart client again. Some relief.

This process repeats, the Client cannot continue running.

I blame the VM because (except for a few BLOCKS), the UI itself stays fast at the *widget* level -- mostly the asynchronous logic parts of the program become slower.

After the UI has had all of its updates, it can be interacted with in low latency and it feels lag free. But when you "load some code" in Eve, it's slow IF the client has degraded.

And it always degrades.

Even though I said the UI remains fast while async logic degrades, I can still feel the asynchronous logic parts of the program blocking the UI in some places. This is actually going on in the trade system's buy/sell/modify dialog! A large amount of the UI can lock up while loading that simple bit of code (Can you please keep it loaded?)

Over time, the client's rate of decline has increased.

I blame either the VM's compiler, or the GC's allocator.

Because,

1) Loading new code becomes slower over time.

2) Loading things which need memory become slower over time.