• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Vista leaks memory in games

J

jjzelinski

Diamond Member
Finally saw it myself first hand a couple of minutes ago, BF2142 was eating 1.6GB ram and climbing, meg by meg. Same thing happens in BF2. What a piece of crap OS that allows this to happen. Now, granted EA deserves blame as well but I know for FACT this doesn't happen in XP.

The sad thing is that I've read about all sorts of people having their games stutter in Vista as if it's some video card thing and it's not; video cards don't make your swap file go nuts throughout the entirety of a game. I suspect that everyone of these people are experiencing the same memory leak. That being said, I can't find anything among my usual sources about this phenomena. Sure, there's thousands and thousand of articles and forum posts bitching about stutter but not ONE of them address the relatively obvious nature of this issue.

I'm about to ditch this POS os, i've had enough.
 
Negative, installed them both yesterday. The problem is superfetch, 100%. I disabled the service and turned it off, smooth as butter now.


So lets see, can't use superfetch because it causes memory leaks in games. Can't use Aero Glass without scrambling the display on my Viewsonic VG2230wm and 7900GT KO every other time I try to login (there's a fix though, it's due to memory timing issues with the 7900GT drivers and vista). So what am I supposed to find appealing about Vista now? lol! Hell, they didn't even include WinFS, but god only knows what havoc that would've wreaked!

Sigh, at least my rant bore productive fruit. Hope the above fix helps all those poor souls dealing with the stuttering.

EDIT: By the way when I say both I mean the 2 hotfixes that were released for both OS versions.

KB9381947 and KB938979

And your link appears dead unfortunately.
 
This is a completely different hotfix: KB940105

You have to specifically request it from MS. I'll see if I can find a better link.
 
Ah, spoke to soon then sorry. Hopefully this will let me turn superfetch back.

EDIT:

I read about this the other day of at Tech Report (forums) and I'd be surprised if this were my issue. Reason being, the KB has to due with memory addressing issues due to video cards with large memory having their data stored in userspace rather than kernel. I'm only running 256MB vram.

Furthermore this has to do with a 2GB virtual address limit per application. I hadn't yet reached that point.

In fact, maybe you can correct me here, but I thought this issue was related to BSODs that occured when the data in vram tried to make a copy of itself in virtual address space that wasn't available anymore due to exceeding the 2GB threshold?
 
Just an update after playing BF2142 for several hours, all is well without superfetch. Still haven't tried the KB recommended above though.
 
I listened to an interview with the leader of the team who created superfetch (Michael Fortan) and they said they might cosider adding a control panel for superfetch later on, depending on how well it works for people.
 
Oh lawdy lawdy lawd. It muss be Vista! Everyone knows EA writes such bug-free games like battlefield. :roll:
 
I ran into a similar problem with WoW... I came to a similar conclusion, but rather than completely disable Superfetch I disabled indexing for the specific files I found it to be accessing constantly and the problem went away. These files were large, multi-GB files, 2 or 3 of them.
 
Originally posted by: Jeff7181
I ran into a similar problem with WoW... I came to a similar conclusion, but rather than completely disable Superfetch I disabled indexing for the specific files I found it to be accessing constantly and the problem went away. These files were large, multi-GB files, 2 or 3 of them.
Click to expand...

which files and how?
 
Originally posted by: clarkey01
Originally posted by: Jeff7181
I ran into a similar problem with WoW... I came to a similar conclusion, but rather than completely disable Superfetch I disabled indexing for the specific files I found it to be accessing constantly and the problem went away. These files were large, multi-GB files, 2 or 3 of them.
Click to expand...

which files and how?
Click to expand...

In here you'll find a debate about it...

Here's the post I made about which file it was and how I disabled it.
 
EA's Battlefield games are two of the most poorly coded and bloated monsters of programming ever to hit store shelves.

Turn your hate to EA. There's a reason why my Source games don't have stupid problems like this. They're not EA games.
 
Originally posted by: Jeff7181
Originally posted by: clarkey01
Originally posted by: Jeff7181
I ran into a similar problem with WoW... I came to a similar conclusion, but rather than completely disable Superfetch I disabled indexing for the specific files I found it to be accessing constantly and the problem went away. These files were large, multi-GB files, 2 or 3 of them.
Click to expand...

which files and how?
Click to expand...

In here you'll find a debate about it...

Here's the post I made about which file it was and how I disabled it.
Click to expand...

Thanks Jeff, noted for later.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top