For what it's worth, the game seems more stable for me. I don't know if this is because of the update or because I reverted to running in windowed (full screen) to get over an issue where alt+tabbing to the desktop would crash the game in true full screen. I played a very long session in Cyrodiil yesterday (over 4 hours) and only crashed once.
[EDIT]Oh, and I no longer get Windows low memory warnings.
I counted 4 crashes in around 3 hours last night in Cyrodiil. The last one I took as a sign I should just give it up and go to bed.
@ZOS break the game on your own time. You've got paying customers to please. With this track record you've created an expectation for low quality among your own fanbase. What do you think they're saying outside the fanbase? You've got limited time to make it right before the next generation of gaming shows up and crushes ESO on all fronts. You've got a console version to refine and it's going to be going head to head with Bungie's Destiny. With the fairly recent announcement that they're coming to PC and Steam by March 2015, you have a $500 million dollar comparative market competitor on your turf whose only negative PR is related to who is getting what content exclusives. Rock solid content by the way, as the recent open *** beta test has it projected to be THE game of late Q3 2014, and no doubt a must have title this holiday season. Meanwhile at Zenimax, you're struggling just to get things working, introducing more problems in every update, and the only time the PR is positive is when they say nothing at all.
Keep it up and you're going to retain only a niche market of dedicated players, and no one else is going to care ESO ever existed. Stop treating your live servers like a beta test platform for future builds, you're doing far more harm to the longevity if the IP than simply delaying patches until they are fully tested, scrutinized, and smoothed out. If you never take the time, you'll never have the time, and we all know time is money... yours is no doubt steadily running out.
SirenofEntropy wrote: »ferzalrwb17_ESO wrote: »The 3.7GB "limit" you're thinking of applies to 32bit Operating systems that reserve some memory for Video processing and other things; not processes within 64bit OS's. Are you sure you watched the game die at this "magic" 3.7GB cap?
I definitely don't have a 32-bit OS. All I know is that every time my game reaches around 3.6-3.7 gb of RAM usage, it crashes. And it's not for my system being out of memory seeing as there's still plenty of free system RAM to spare when it happens.
Even if there's some other reason for the crashing, should this game client REALLY be using over 3.5 gb of RAM in a relatively short playing session? No, especially not when it's using a 32-bit client.
SirenofEntropy wrote: »Even if there's some other reason for the crashing, should this game client REALLY be using over 3.5 gb of RAM in a relatively short playing session? No, especially not when it's using a 32-bit client.ferzalrwb17_ESO wrote: »The 3.7GB "limit" you're thinking of applies to 32bit Operating systems that reserve some memory for Video processing and other things; not processes within 64bit OS's. Are you sure you watched the game die at this "magic" 3.7GB cap?
DenverRalphy wrote: »SirenofEntropy wrote: »Even if there's some other reason for the crashing, should this game client REALLY be using over 3.5 gb of RAM in a relatively short playing session? No, especially not when it's using a 32-bit client.ferzalrwb17_ESO wrote: »The 3.7GB "limit" you're thinking of applies to 32bit Operating systems that reserve some memory for Video processing and other things; not processes within 64bit OS's. Are you sure you watched the game die at this "magic" 3.7GB cap?
Actually, yes, it should. Unused RAM is wasted RAM. As long as the memory is cleared/cleaned when needed, or upon closing/shutting-down the program, then yes, it should use all available resources.
DenverRalphy wrote: »SirenofEntropy wrote: »Even if there's some other reason for the crashing, should this game client REALLY be using over 3.5 gb of RAM in a relatively short playing session? No, especially not when it's using a 32-bit client.ferzalrwb17_ESO wrote: »The 3.7GB "limit" you're thinking of applies to 32bit Operating systems that reserve some memory for Video processing and other things; not processes within 64bit OS's. Are you sure you watched the game die at this "magic" 3.7GB cap?
Actually, yes, it should. Unused RAM is wasted RAM. As long as the memory is cleared/cleaned when needed, or upon closing/shutting-down the program, then yes, it should use all available resources.
SirenofEntropy wrote: »DenverRalphy wrote: »SirenofEntropy wrote: »Even if there's some other reason for the crashing, should this game client REALLY be using over 3.5 gb of RAM in a relatively short playing session? No, especially not when it's using a 32-bit client.ferzalrwb17_ESO wrote: »The 3.7GB "limit" you're thinking of applies to 32bit Operating systems that reserve some memory for Video processing and other things; not processes within 64bit OS's. Are you sure you watched the game die at this "magic" 3.7GB cap?
Actually, yes, it should. Unused RAM is wasted RAM. As long as the memory is cleared/cleaned when needed, or upon closing/shutting-down the program, then yes, it should use all available resources.
If that's true then maybe the issue here is that it ISN'T getting cleaned out when it should, thus it ends up ballooning over the limit of what a 32-bit client can handle.
ferzalrwb17_ESO wrote: »DenverRalphy wrote: »SirenofEntropy wrote: »Even if there's some other reason for the crashing, should this game client REALLY be using over 3.5 gb of RAM in a relatively short playing session? No, especially not when it's using a 32-bit client.ferzalrwb17_ESO wrote: »The 3.7GB "limit" you're thinking of applies to 32bit Operating systems that reserve some memory for Video processing and other things; not processes within 64bit OS's. Are you sure you watched the game die at this "magic" 3.7GB cap?
Actually, yes, it should. Unused RAM is wasted RAM. As long as the memory is cleared/cleaned when needed, or upon closing/shutting-down the program, then yes, it should use all available resources.
Umm.... I think Zeni has a job for you.
SirenofEntropy wrote: »DenverRalphy wrote: »SirenofEntropy wrote: »Even if there's some other reason for the crashing, should this game client REALLY be using over 3.5 gb of RAM in a relatively short playing session? No, especially not when it's using a 32-bit client.ferzalrwb17_ESO wrote: »The 3.7GB "limit" you're thinking of applies to 32bit Operating systems that reserve some memory for Video processing and other things; not processes within 64bit OS's. Are you sure you watched the game die at this "magic" 3.7GB cap?
Actually, yes, it should. Unused RAM is wasted RAM. As long as the memory is cleared/cleaned when needed, or upon closing/shutting-down the program, then yes, it should use all available resources.
If that's true then maybe the issue here is that it ISN'T getting cleaned out when it should, thus it ends up ballooning over the limit of what a 32-bit client can handle.
I usually assume if somebody knows enough to identify it as a memory leak instead of just a crash, that they probably, you know, know what it is.
I usually assume if somebody knows enough to identify it as a memory leak instead of just a crash, that they probably, you know, know what it is.
Most people don't know what a Memory Leak is or how it manifests itself. It's a term they heard, sounds cool, and they throw it out whenever there is a problem with a game or program. For example, a loop in a program can tie up memory resources to the point where a program can crash, but it's not a Memory Leak.
http://en.wikipedia.org/wiki/Memory_leak
There are many reasons why a PC Program will crash, and those reasons are multiplied when a server and the internet is involved.
DenverRalphy wrote: »SirenofEntropy wrote: »DenverRalphy wrote: »SirenofEntropy wrote: »Even if there's some other reason for the crashing, should this game client REALLY be using over 3.5 gb of RAM in a relatively short playing session? No, especially not when it's using a 32-bit client.ferzalrwb17_ESO wrote: »The 3.7GB "limit" you're thinking of applies to 32bit Operating systems that reserve some memory for Video processing and other things; not processes within 64bit OS's. Are you sure you watched the game die at this "magic" 3.7GB cap?
Actually, yes, it should. Unused RAM is wasted RAM. As long as the memory is cleared/cleaned when needed, or upon closing/shutting-down the program, then yes, it should use all available resources.
If that's true then maybe the issue here is that it ISN'T getting cleaned out when it should, thus it ends up ballooning over the limit of what a 32-bit client can handle.
It can't balloon over. The kernel won't allow for it. Memory leaks are caused by dynamic objects being created, but not being destroyed when they are no longer relevant. The symptoms of a memory leak is a dramatic slowdown after memory is full and the onboard storage (ie the hard drive) is utilized for memory management (basically memory and hard drive is swapping data).
Unless your hard drive is full and can no longer handle the swapfile mechanic. Basically your memory would have to be full, and your drives as well before a crash occurs.
DenverRalphy wrote: »starlizard70ub17_ESO wrote: »NerfEverything wrote: »Here we go again with people who have no understanding of how computers work blaming a "memory leak" for their game crashes. I'm sick of this.
Except my Alienware Aurora with i7 930 processor, 16g Ram, and a nVidia 651i 2g video card, played this game fine with a few crashes from time to time before 1.3.3. But after the patch, I crash every 10 to 15 mins in game now. Plus I can play Bioshock Infinite, Thief, Far Cry 3 and a host of other highend, heavy graphic games at max settings with no problems. I guessing it was the patch that broke something in ESO, causing the memory leak and other problems.
And yet many many gamers with lower specs are not suffering the same symptoms. Kindly show evidence that it's a memory leak causing the crashes. After all... Memory leaks are not the sole cause of crashes. There are literally thousands of other causes.
I had a new bug in cyrodiil that the longer i play the more damage my abilities do, this bug just happens to be just before a crash to desktop (maybe a new memory leak bug or something with my skills setup).
This game is *** honestly and serioiusly
ferzalrwb17_ESO wrote: »DenverRalphy wrote: »SirenofEntropy wrote: »DenverRalphy wrote: »SirenofEntropy wrote: »Even if there's some other reason for the crashing, should this game client REALLY be using over 3.5 gb of RAM in a relatively short playing session? No, especially not when it's using a 32-bit client.ferzalrwb17_ESO wrote: »The 3.7GB "limit" you're thinking of applies to 32bit Operating systems that reserve some memory for Video processing and other things; not processes within 64bit OS's. Are you sure you watched the game die at this "magic" 3.7GB cap?
Actually, yes, it should. Unused RAM is wasted RAM. As long as the memory is cleared/cleaned when needed, or upon closing/shutting-down the program, then yes, it should use all available resources.
If that's true then maybe the issue here is that it ISN'T getting cleaned out when it should, thus it ends up ballooning over the limit of what a 32-bit client can handle.
It can't balloon over. The kernel won't allow for it. Memory leaks are caused by dynamic objects being created, but not being destroyed when they are no longer relevant. The symptoms of a memory leak is a dramatic slowdown after memory is full and the onboard storage (ie the hard drive) is utilized for memory management (basically memory and hard drive is swapping data).
Unless your hard drive is full and can no longer handle the swapfile mechanic. Basically your memory would have to be full, and your drives as well before a crash occurs.
Somebody's been googling I see...
DenverRalphy wrote: »starlizard70ub17_ESO wrote: »NerfEverything wrote: »Here we go again with people who have no understanding of how computers work blaming a "memory leak" for their game crashes. I'm sick of this.
Except my Alienware Aurora with i7 930 processor, 16g Ram, and a nVidia 651i 2g video card, played this game fine with a few crashes from time to time before 1.3.3. But after the patch, I crash every 10 to 15 mins in game now. Plus I can play Bioshock Infinite, Thief, Far Cry 3 and a host of other highend, heavy graphic games at max settings with no problems. I guessing it was the patch that broke something in ESO, causing the memory leak and other problems.
And yet many many gamers with lower specs are not suffering the same symptoms. Kindly show evidence that it's a memory leak causing the crashes. After all... Memory leaks are not the sole cause of crashes. There are literally thousands of other causes.
As I have kept saying in various threads, my entire group of 18 were constantly being kicked to desktop (in Cyrodiil on EU), sometimes all at the same second so that doesn't look like a memory leak to me, but it does look like a problem at Zenimax's end.
Someone else posted here
http://forums.elderscrollsonline.com/discussion/124637/fun-with-the-crazy-damage-scalating-bug/p1I had a new bug in cyrodiil that the longer i play the more damage my abilities do, this bug just happens to be just before a crash to desktop (maybe a new memory leak bug or something with my skills setup).
So something is going screwy somewhere
I never cry memory leak, but this time it's pretty obvious. Relog ever couple hours and I'm fine, but I've watched my client memory usage creep 1.2(normal) to 3.6 over the course of those hours. It crashes at that point. Myabe it's not a "mem leak" but it certainly something.NerfEverything wrote: »Here we go again with people who have no understanding of how computers work blaming a "memory leak" for their game crashes. I'm sick of this.
Instant Weapon Swap
We’ve made changes to the way we cache textures for your alternate weapon that will allow you to swap weapons reliably and instantly. The previous delay when swapping has been reduced significantly, so swapping to your second ability set will be seamless and fast, making combat feel more responsive.
lordrichter wrote: »I am curious... Is anyone who is experiencing the out of memory error (memory leak) using weapon swapping?Instant Weapon Swap
We’ve made changes to the way we cache textures for your alternate weapon that will allow you to swap weapons reliably and instantly. The previous delay when swapping has been reduced significantly, so swapping to your second ability set will be seamless and fast, making combat feel more responsive.
SirenofEntropy wrote: »Nope, the character I was predominantly crashing on is only level 8 and therefore not even able to weapon swap yet. So it's unlikely this has anything to do with it.
freespirit wrote: »OK.........
Windows Vista 32 bit
3GB Ram
Intel (R) Core Quad CPU Q6600 @ 2.4GHz
AMD Radeon HD 6570
No crashes since Update 1.3.3......
Not even in Cyrodiil..........
EU server