As this issue seems to have been resolved with new drivers I'll mark this thread as solved now.
Even with Catalyst 14.6 Beta didn't fix this OTZ
June 3. patch and 14.6 beta both fixed nothing related to the memoryleak.
As much as it pains me to say this, EA/AMD is never going to fix this issue.
EA:
Lets be honest for a minute, BF4 is no longer EA's top game - Watch Dogs is. They are releasing DLC before that game has had its bugs ironed out. The reality is, I'm sure some people at EA may care about this and know about this but they aren't in a position to fix this bug/don't care enough to fix the bug. Perhaps these people view it solely as an AMD driver problem and thus something AMD needs to fix. If EA was actually interested in fixing this it would have been fixed by now. There was a time where they cared about thier customers and listened to forums like this one but those days are long gone. I have been checking in on this forum weekly for months now (since last november) and I gotta say, if a fix hasn't happened by now, it's not gonna happen. BF4 is aging and is no longer a top priority for them. We should simply accept it as a loss and move on if we aren't in a position to get an Nvidia GPU. Fair? Nope. Reality in the face of a greedy as fu#k company? Yup.
AMD:
I have a lot more respect for AMD than I do EA but they don't seem to care about this issue either. Again, I'm sure a team of people at AMD are aware of this bug but either aren't in a position to fix it or would rather point the finger at EA and blame it as a bf4 issue not an AMD issue. If AMD was interested in fixing it it would have been fixed by now.
Conclusion:
There is only 4 possible causes for this bug:
1. EA has a bug in BF4 that needs to be patched to allow it to play nice with Radeon HD 5xxx 6xxx and 7xxx cards. (EA at fault)
2. AMD has something in thier drivers that is incompatible with bf4 and is causing this bug. (AMD at fault)
3. A combination of 1 and 2 requiring engeneers from both companies to work together to fix the issue. (EA and AMD at fault)
4. Windows 8 is different enough from previous versions of windows that 1 and 2 together are both at fault but only when windows 8/8.1 is involved. (EA's fault, AMD's fault, or EA and AMD's fault)
My opinion is that privately EA points the finger at AMD and AMD points the finger and EA and that perhaps they both also point a second finger at changes in windows 8/8.1. They likely both think that the other didn't code the drivers (AMD) or the game (EA) correctly to interact with windows 8/8.1 while running bf4.
This is a giant cluser fu#k that driver engeneers from AMD and game engeneers for BF4 from EA need to sit down together and fix. The reality is there likley needs to be changes on both sides to play with each other and windows 8/8.1 nicer. BUT both companies are so busy that if it hasn't happened by now this meet up and bug fixing will never happen - especially because it only affects 5xxx 6xxx and 7xxx series of cards and the accepted "fix" is buy a new GPU. Complete bull **bleep**? Yup. Must we sit there and take it knowing a fix won't ever come? Unfortunately yes.
Thats my two cents at least....
EDIT - Yes Watch Dogs in Ubisofts not EA's - EA is still a piece of * company though for not caring enough to fix this, my statement still stands bf4 is not their top priority any longer
@MeleeMike wrote:As much as it pains me to say this, EA/AMD is never going to fix this issue.
EA:
Lets be honest for a minute, BF4 is no longer EA's top game - Watch Dogs is. They are releasing DLC before that game has had its bugs ironed out. The reality is, I'm sure some people at EA may care about this and know about this but they aren't in a position to fix this bug/don't care enough to fix the bug. Perhaps these people view it solely as an AMD driver problem and thus something AMD needs to fix. If EA was actually interested in fixing this it would have been fixed by now. There was a time where they cared about thier customers and listened to forums like this one but those days are long gone. I have been checking in on this forum weekly for months now (since last november) and I gotta say, if a fix hasn't happened by now, it's not gonna happen. BF4 is aging and is no longer a top priority for them. We should simply accept it as a loss and move on if we aren't in a position to get an Nvidia GPU. Fair? Nope. Reality in the face of a greedy as fu#k company? Yup.
AMD:
I have a lot more respect for AMD than I do EA but they don't seem to care about this issue either. Again, I'm sure a team of people at AMD are aware of this bug but either aren't in a position to fix it or would rather point the finger at EA and blame it as a bf4 issue not an AMD issue. If AMD was interested in fixing it it would have been fixed by now.
Conclusion:
There is only 4 possible causes for this bug:
1. EA has a bug in BF4 that needs to be patched to allow it to play nice with Radeon HD 5xxx 6xxx and 7xxx cards. (EA at fault)
2. AMD has something in thier drivers that is incompatible with bf4 and is causing this bug. (AMD at fault)
3. A combination of 1 and 2 requiring engeneers from both companies to work together to fix the issue. (EA and AMD at fault)
4. Windows 8 is different enough from previous versions of windows that 1 and 2 together are both at fault but only when windows 8/8.1 is involved. (EA's fault, AMD's fault, or EA and AMD's fault)
My opinion is that privately EA points the finger at AMD and AMD points the finger and EA and that perhaps they both also point a second finger at changes in windows 8/8.1. They likely both think that the other didn't code the drivers (AMD) or the game (EA) correctly to interact with windows 8/8.1 while running bf4.
This is a giant cluser fu#k that driver engeneers from AMD and game engeneers for BF4 from EA need to sit down together and fix. The reality is there likley needs to be changes on both sides to play with each other and windows 8/8.1 nicer. BUT both companies are so busy that if it hasn't happened by now this meet up and bug fixing will never happen - especially because it only affects 5xxx 6xxx and 7xxx series of cards and the accepted "fix" is buy a new GPU. Complete bull **bleep**? Yup. Must we sit there and take it knowing a fix won't ever come? Unfortunately yes.
Thats my two cents at least....
Watch_Dogs is Ubi's man.
And as far as I recall I used to bump into this problem in BF3 also. After I upgraded my RAM from 4 to 8 gig it stopped, but my BF3 is 32bit version so I guess it couldn't chew off more than 3.2 gig.
I do agree that this thing will most likely be left unsolved, at least intentionally, from the devs' side. However after the 2nd most recent patch for BF4, somehow the leak stopped for me. I'm not sure if it stopped definitely or just delayed but now I can game for 2 hours straight without any incident. After every match I alt tab out to check the task manager and kill the process if the leak occurs, so maybe the alt tab thing now works for me lolz.
I thought this problem was fixed for the 7000 series+ cards.. with drivers, thats one of the things that made me mad in the first place, I thought they just abandoned the older cards drivers and fixed only for the newer..
now I see some guy got this problem even with r9 280x .. like seriously what a joke !
Are you sure it's from BF4 though ?
Did you try updating your NIC/ethernet chipset driver ? I heard there is a memory leak problem with that too
What I find strange too is there there should be more people having this problem and complaining...
Also I noticed I had my page file manually set.. if it's the case for you too try to put it on auto.
Oh and I didnt had this problem since the last time I had it and reinstalled drivers etc..strange.
I also ordered a gtx 770 and installed, then I sent it back cause I was disapointed at the performance, started lagging with vsync on, and now after reinstalling drivers for this card maybe it fixed it ??
Maybe you guys who keep having this problem could try something to experiment..
Uninstall your AMD drivers, install Nvidia drivers (not sure if you can without a nvidia card on though..) and uninstall it and reinstall the latest nvidia.. just trying to help
Gonna do more testing..
