http://bugs.winehq.org/show_bug.cgi?id=16456
--- Comment #44 from Jeffrey Bonggren 7wtjvu302@sneakemail.com 2009-03-26 17:09:47 --- (In reply to comment #43)
For users (e.g. Jeffrey Bonggren and I guess thefirstkeet@gmail.com, too), with x86_64 + nvidia (G80+) + something more than 3GB ram, please have a look here: http://www.nvnews.net/vbulletin/showthread.php?t=127984 and try the workarounds mentioned there. It would be nice, if you could add some system information from your system, where the problem is reproduce able. Hopefully the bug will be fixed soon.
The problem mentioned in the nvnews thread is AFAICT unrelated to wine, except to the extent that most (all?) programs run in Wine are 32-bit.
I compiled and ran the two test programs (leaktest.c and leaktest_v2.c) from this post http://www.nvnews.net/vbulletin/showpost.php?p=1945813&postcount=36 in that thread. The glClear()/glFlush() memory leak did not manifest itself on my system.
The only general problem I have had with my NVIDIA card is that I can't start X without instantly hanging the whole system (with my caps and scroll-lock lights turning on!) on any NVIDIA drivers newer than 177.82. I don't want to waste space here troubleshooting my 3D setup. I just want to make clear that it doesn't appear to be relevant to this GL_OUT_OF_MEMORY bug.