LexonLightbringer wrote: »

Hero Engine = Memory Leaks / see SWTOR for more details about Hero Engine and memory leaks!

I'll say it again for the humpteenth time. ESO Does NOT use the Hero Engine! They only used it at first to see how assets would perform in a MMO enviroment, it was a test bed!

Before patch my game ran rock solid. Since patch, the game eats my memory up in under 20 minutes. It caches hard and goes total apeshit on my harddrive. Shutting the game down means a 20 minute wait of a black screen before my desktop reappears.

dinges wrote: »

Yea i saw a bunch of them and they are probably right. All i'm saying is that a executable from a game like this is intended to grow. Just open up the game (don't even login) and check the eso.exe (it will grow).

Yes but if it reaches around the 4GB mark then it will crash out. Don't forget ESO is a 32bit executable but is LAA (Large Address Aware). I found that pre-this patch the it never used above 2GB but will be interesting to see its current size post patch.

Same here. this is the only game that makes me continuously ctd......Why can't they fix this?

I never had this problem before

Loxy37 wrote: »

Sakiri wrote: »

Loxy37 wrote: »

dinges wrote: »

Yea i saw a bunch of them and they are probably right. All i'm saying is that a executable from a game like this is intended to grow. Just open up the game (don't even login) and check the eso.exe (it will grow).

Yes but if it reaches around the 4GB mark then it will crash out. Don't forget ESO is a 32bit executable but is LAA (Large Address Aware). I found that pre-this patch the it never used above 2GB but will be interesting to see its current size post patch.

Its gone over 2.1 and choked my system out.

It actually asked me if I wanted to disable Aero today.

Wow. I was looking forward to the patch but now I'm kinda worried as I'm still stuck with 4GB ram until the next few months. Feel sorry for anyone using a 32bit OS.

Ive got 4gb and until my trip to EU in April is done I dont see it being rectified.

Using x64 win7 ultimate.

The 2.1gb usage was in shadowfen before this patch.

For people having lag or in-game crashes, especially after playing for several minutes, this memory leak is part of the reason why.

I confirmed this this morning. Memory usage started out at 85 MB. In a 2 steps forward, 1 step back fashion it has risen to 122 MB over 30 minutes. As expected there has been no disk usage. The launcher will call home to the tune of 0.1 mb/s network usage. No problem there. Oddly it is using 0.8% to 1.3% CPU with one spike to over 5%. While of note this doesn't look like anything that would impact my gameplay as this represents 1% of my CPU and 5% of my memory. I will keep my task manager open and Alt-Tab to it occasionally as I play to see what it looks like in game.

Actually launching to character select the client resulted in the game process starting with 15.7% CPU and 187.9 MB memory usages.

I am now logged in to one of my nerfed to useless templars. Game CPU usage is 22.6%. RAM is 1089 MB. The launcher stays active with 0.3 CPU and 78 MB RAM. With both CPU and RAM usages in the low 20% range this presents no problems for me. It may for others however. I wonder if those with limited systems could benefit from closing the launcher once in game or if that would screw something up. I'l give it a try and see.

i had the memo leak to before the patch, also wrote a post about it some time ago where i mentioned it in, so if it has gotten worse then....
meh...
They should have fixed that issue a long time ago tbh

If the game uses the Hero engine we are in for a ride i can tell you...
That engine sucks donkey ba..s big time!

That leak got proved for PC to and at eu server to.
9!GB of shared RAM full and game crash. Within 1 hr

Twiddling my thumbs while EU client updates

dinges wrote: »

And then it's funny to see non-coders look at how an app runs Start up nearly anything within windows and put it to dorment.. You will see it grow regardless how small. Windows garbage collection is responsible for releasing the memory parts within an executable.

Then its broken or does unneeded memory thrashing while idle.

PS: OS Memory Management != GC, and even not all GC's are equal (Java's work different to .NET and there are even differences between .NET versions)

dinges wrote: »

You can't control garbage collection, it's something that launches when microsoft/windows has enough criteria met to state your pc has enough breathing room to release the garbage.. Runs badly on nearly ever app i code, especially within .NET.

Once again, either you are mixing things or I am misinterpreting what you say.

Looking from an application's view (I am not going to go into kernel vs userland), you have two levels of memory management:

• that which the OS does, which handles allocating/freeing memory applications ask for, swapping when availability goes down, caching, etc.
• that which the application does, for which I will just list 2 broad catagories:
  1. unmanaged (your traditional ASM/C/C++/etc. with no free memory management or runtime checking) - a term only really brought into play by managed code
  2. managed (.NET VC/C#/ managed C++, Perl, Python, Java, etc. with GC, etc. "for free")

The "for free" I throwed in there because you can still do stupid things that screw up referencing and causing leaks, and some resources like some handles and network sockets are not always managed. Also bad code can cause memory thrashing which decrease performance and increase memory usage. Lastly, some GC's enable you to explicitly do a GC with more or less success depending on the GC implementation (and on when its called in the application - too often or at all depending on the GC could also be a no-no).

dinges wrote: »

Runs badly on nearly ever app i code, especially within .NET.

Just quoting this again to make another point: will have to see when I can get into the game again, but the launcher at least do not use .NET, so they have to manage memory (and other resources like handles, etc.) on their own.

Try:

tasklist /m "mscor*"

dinges wrote: »

Thanks for reporting OP, but what you post is how windows works from 2.11 and on...

Nope, 2.11 did not have for example swap support as far as I can determine. Besides, each new major release brought improvements to to memory management (OS side) and other features - PAE in 2k, LAA in XP and even Win8 have Memory Combining, etc. not available fore Win7.

dinges wrote: »

Yea i saw a bunch of them and they are probably right. All i'm saying is that a executable from a game like this is intended to grow. Just open up the game (don't even login) and check the eso.exe (it will grow).

Interestingly ... no. Currently have been watching Bethesda.net_Launcher.exe downloading the update for the last hour or so, and it sits happily fluctuating from between 127-138MB in long even curves. We will see after the patch though...

dinges wrote: »

Leave it open, unplug your network cable or WiFi and you should instantly see that the memory gets released and the growing stops.

Which tells me there is a leak somewhere. I agree that with the polling of the news feed there should be fluctuation, but just growing forever?

dinges wrote: »

@GossiTheDog‌ : Don't know if you are already logged in but check the load on having the launcher open as well. Both use the same message delivery system and BOTH are eating up memory. Most people keep the launcher open after going into the game. It would make a big difference to close the launcher after going in the game. (ctrl-shift-esc, check mem loads)

I usually have the launcher running for days without restarting, and as of yet I had no issues - once again will see after the patch.

Loxy37 wrote: »

dinges wrote: »

Yea i saw a bunch of them and they are probably right. All i'm saying is that a executable from a game like this is intended to grow. Just open up the game (don't even login) and check the eso.exe (it will grow).

Yes but if it reaches around the 4GB mark then it will crash out. Don't forget ESO is a 32bit executable but is LAA (Large Address Aware). I found that pre-this patch the it never used above 2GB but will be interesting to see its current size post patch.

Depends. If they are using AWE (Address Windowing Extensions), it could go past 4GB if your system have more - else it might thrash the swap like hell or crash without AWE (or with - not sure what AWE will do in trying to use more than 4GB with only 4GB system memory).

I've played a good bit this morning. In and out of instances, switched to a half dozen toons for inventory management, did a bit of crafting, etc. Even after all of that my CPU usage is at 23.8 and RAN usage is 2106 MB. I ended task on the launcher as well. That had no effect on gameplay other than freeing up a bit of resources. Even with Chrome running multiple tabs and the task manager running and a plethora of background processes CPU and RAM are in the mid to upper 20% range. I'll keep at it to see if there are any changes.

Win 8.1 pro 64 bit, Intel 2nd gen i7, GeForce GTX 660 ti, 20 GB RAM.