Tweet
Joy of joys
Posting in off topic since I'm not really unsupportable, nor do I want tech help (since I basically know the problem). I just wanna bitch.
So, turns out I'm the proud new owner of a memory leak. Well, sorta. Last few times I've played Batman: Arkham Asylum on my PC, I've noticed it chug a fair bit at certain sections, usually while loading. Strangely, turning down the PhysX and Anti-Aliasing seemed to help for a while. Tried turning it back up today, and after about an hour or two, the game basically became unplayable, since I was at a stealth section, and playing on hard, so I had to restart from the checkpoint a few times. Each time, the loads got longer and longer. Finally got up to just over a minute. Fuck that. I quit to the menu. Takes over a minute just to get to the menu. Now that the sound's cut out, I can hear my HDD giving a good go. I figured maybe I had a scan going on or something. That'd tend to slow down load times. Finally, after about 2 minutes, I'm able to quit to the desktop, which *also* takes about a minutes. At this point, I'm starting to panic. Did I burn out something in my system? Start system monitor, and I'm running at 99% capacity for RAM usage. Well fuck. There's my issue. And I know it's Batman doing it, since even after I quit, it was still running and taking up over 80MB of RAM itself (doesn't sound like much, until I remind you it wasn't actually running), and then all its little attendant processes. Fuckin' eh. Quick math showed me I wasn't being shown *nearly* enough RAM usage to actually account for that percentage, so, RAM leak. I'll confirm by running it again with no PhysX, and see how it does, but I'm willing to bet that solves it.
I've been running this build virtually unmodified for two years (replaced the video card back in Feb. or so, and that's it), and this is the first time I've seen my comp crack the 2.5 GB usage mark. I've maxed all four cores, beat up on my video card, but my RAM's always been more than up to the challenge. Frakkin' Batman.
So, turns out I'm the proud new owner of a memory leak. Well, sorta. Last few times I've played Batman: Arkham Asylum on my PC, I've noticed it chug a fair bit at certain sections, usually while loading. Strangely, turning down the PhysX and Anti-Aliasing seemed to help for a while. Tried turning it back up today, and after about an hour or two, the game basically became unplayable, since I was at a stealth section, and playing on hard, so I had to restart from the checkpoint a few times. Each time, the loads got longer and longer. Finally got up to just over a minute. Fuck that. I quit to the menu. Takes over a minute just to get to the menu. Now that the sound's cut out, I can hear my HDD giving a good go. I figured maybe I had a scan going on or something. That'd tend to slow down load times. Finally, after about 2 minutes, I'm able to quit to the desktop, which *also* takes about a minutes. At this point, I'm starting to panic. Did I burn out something in my system? Start system monitor, and I'm running at 99% capacity for RAM usage. Well fuck. There's my issue. And I know it's Batman doing it, since even after I quit, it was still running and taking up over 80MB of RAM itself (doesn't sound like much, until I remind you it wasn't actually running), and then all its little attendant processes. Fuckin' eh. Quick math showed me I wasn't being shown *nearly* enough RAM usage to actually account for that percentage, so, RAM leak. I'll confirm by running it again with no PhysX, and see how it does, but I'm willing to bet that solves it.
I've been running this build virtually unmodified for two years (replaced the video card back in Feb. or so, and that's it), and this is the first time I've seen my comp crack the 2.5 GB usage mark. I've maxed all four cores, beat up on my video card, but my RAM's always been more than up to the challenge. Frakkin' Batman.
Comment