Battlefield will get memory leak issue to the exttent that 90% or more ram is used. Either the game will crash on its own or sometimes it just gets so bad for a few minutes that I just kill the game on my own. Either way, both methods of the game terminating result in memory staying used and there is no evidence of any process/application using the memory. I log off and back on and the memory is still used up, so reboot was necessary.
Prior to the last client update, I was able to reboot the PC and clear the issue...and log back in to repeat the problem again in 15 to 30 minutes time. However, as of this last update now when the game crashes rebooting does not restore the memory back normal utilization. I have to tweak the pagefile settings on/off or inrease/decrease...anything seems to work - then reboot the computer to release the memory. This is very odd!!!! Computer tests clean with multiple AV/Malware tools.
I also have the typical audio issues (sound cuting in/out at times on some maps), but other than the memory leak I have seen great improvement in playability since the last update. I just wish the crashing would go away.
Dell XPS
8 GB RAM
Windows 8.1 Pro 64bit
AMD Radeon HD 6700
Catalyst 13.11 Beta9 (same issue with Beta7 and 8, also pre 13.11 drivers)
Samsung SSD 840 Hard Drive
Pagefile on non SSD drive
machofreek, sounds like you're suffering from something other than the memory leak (or more than just the memory leak). There is no way BF4 can use up your memory on a fresh reboot when it hasn't even been loaded yet.
You're doing a full reboot, what is your Non-paged pool at before loading anything?
Just to recap, I've been going strong for 4 days now I think, no crashes at all (besides servers crashing, great $100 investment EA, god forbid you give us some money back on your bloated server prices when you exclude us from quick join just to be able to move people to squads and use team balance mods)
I did the registry edit mentioned here, that didn't help, then I did the Windows 7 compatibility mode and disabled the display scaling in the compatitiblity tab for BF4.exe and haven't had the leak since.
Windows 8.1 Pro with WMC
XFX Radeon 6970 with 13.11 Beta 9.2 drivers
8GB DDR3 1866
Intel i7-2700k @4.7GHz
Asus P8z77-V LE
Corsair Force GS SSD
Page File is disabled
You have no idea what you are talking about. You absolutely do not need virtualization to run 32-bit processes on a 64-bit os. an x86_64 processor can natively run 32-bit code, and all the 32-bit compatibility stuff in windows is handled by a windows subsystem called WOW64, there is no virtualization involved.
And this doesn't have anything to do with the memory leak anyway.
@bwat47 - I believe I have found a temporary solution. Checking "Disable display scaling on high DPI settings" combined with Win 8 compatibility mode.
Don't ask me why that should prevent the memory leak but haven't had one in about the last 18hrs of play. Logged a total of around 110hrs ingame as of tonight.
I'm not saying it's a fix but it's certianly held it at bay more. Still up around 12th for Sniper kills in Aussie, now to get back up to 5th...
@porkysatan
You have absolutely no idea what you are talking about. Virtualization options in the BIOS enable the CPU's hardware virtualization flags for Intel VT.
http://ark.intel.com/products/virtualizationtechnology
This is hardware emulation for virtualization applications such as VMWare and XEN. Get a clue.
Seriously, I fully powered off the machine (not just reboot) and it stayed at same memory usage level as when BF4 crashed out to desktop. Being in the IT field for over 20 years I know this sound highly improbable. It was as if the computer was going to sleep and not actually rebooting.
I ended up manually uninstalling the C++ 2012 Runtime verison installed by the video drivers. I then uninstalled the video drivers as well. I shutdown and then installed the 13.11 Beta8 drivers. I figured I would go back to them since I didn't have the problem I mentioned with stuffed memory on reboot until Beta9 drivers and the last update.
Game can sometimes go about 30 minutes, a few maps before memory leak. However, maps like Dam and Flood seem to be a given that it will memory leak by the time the map changes over.
The next time I play and get the leak I'll post the non-paged pool. Right now with things idle it is at 396MB Paged Pool / 99.9MB Non-Paged Pooled. Memory is still steady at 18% utilization.
Running BF4(x64) in windows 8 compatibility mode seems to do the trick. Now if only AMD would do something about it.
I'm using a 6970 on windows 8.1.
Using Catalyst13.11 Beta8 drivers. Memory leak occured mid-game about 30 minutes into play. When the game stopped and I was looking at the battlelog screen, I recorded my memory/page use.
In use 5.8GB / Available 2.2GB
Committed 6.7/20.0GB
Cached 944MB
Paged pool 526MB
Non-Paged pool 4.6GB
Previously with 13.11 Beta9 drivers it would get up to 90%+ memory utilization and the whole machine would slow to a grind. However, with Beta8 drivers it appears the leak isn't absorbing as much of the memory. With a sliver of memory left and the computer still responsive, I joined a game to see what would happen and to my suprise the game ran flawlessly for a couple hours. I exited the game under my own will, so it was nice to have a couple hours of play without issue.
In use 5.6GB / Available 2.4GB
Committed 6.6/20.0GB
Cached 940MB
Paged pool 527MB
Non-Paged pool 4.5GB
A quick reboot and the memory is freed up. I can live with one memory leak crash to the desktop over the span of about 3 hours.
@machofreek wrote:Seriously, I fully powered off the machine (not just reboot) and it stayed at same memory usage level as when BF4 crashed out to desktop. Being in the IT field for over 20 years I know this sound highly improbable. It was as if the computer was going to sleep and not actually rebooting.
I ended up manually uninstalling the C++ 2012 Runtime verison installed by the video drivers. I then uninstalled the video drivers as well. I shutdown and then installed the 13.11 Beta8 drivers. I figured I would go back to them since I didn't have the problem I mentioned with stuffed memory on reboot until Beta9 drivers and the last update.
Game can sometimes go about 30 minutes, a few maps before memory leak. However, maps like Dam and Flood seem to be a given that it will memory leak by the time the map changes over.
The next time I play and get the leak I'll post the non-paged pool. Right now with things idle it is at 396MB Paged Pool / 99.9MB Non-Paged Pooled. Memory is still steady at 18% utilization.
I have an Sapphire 6850.
I've had the same memory usage problem... if I immediately shutdown, and I mean totally shut down my machine, and wait only a half minute or so before booting my machine back up, the memory usage is still at the same 80%+ that I left it when bf4 slowed to a slow stutter. Very odd. If I shutdown and don't touch my machine for a good long while after a bf4 memory spike, the computer boots up with the memory usage being fine.
I am on guard now; whenever I play bf4 (when it lets me play for more than 7 minutes before crashing with a bf4 has stopped working error) and I start to see even the slightest choppiness, I exit the game and check my memory usage. It is usually at about 80% at least (of 16 gigs). I have seen it go to 98%. tonight I was able to play one full map and most of the way through a second round of conquest before the memory usage became a burden.
It has to be because we all have 5000 or 6000 series ATI cards. If anyone is having this problem who DOES NOT have a 5000 or 6000 series ATI card please respond.
I spoke to EA today and tried to get my money back on my premium and bf4 pre-order. That was a fail... I will repost when I get my new ATI card from newegg and try that out.
We have to report the error so that they know
http://www.amdsurveys.com/se.ashx?s=5A1E27D25AD12B60
@AskEASupport
@AMDRadeon
