wine users - Feb 2009 - programs through wine crashing

I put a new video card in a previously stable system, no other changes.
Now WoW, Ventrilo, and City of Heroes all work for a little while then
crash, sometimes with an error message, sometimes without.

System:
AMD Phenomx4, 5gig RAM
Fedora core 10 x64, installed from disk, fully updated
Wine 1.1.14, installed through yum
New video card: Nvidia geforce 9800gt, 1gig memory
Current video driver: Nvidia 180.29, installed as part of Fedora system
updates.

I saw the info on wineappdb about a memory allocation issue in Wine with
systems over 4gig of RAM, but this same computer set up ran perfectly
stable with the old video card (on the mainboard nvidia 6150se, shared
memory) so I was assuming the problem was not that.

I tried putting all in game video settings to minimum and it took longer
but still crashed. When ran from terminal WoW either gives me no error
on crash or gives me this one:

*** glibc detected *** C:\Program Files\World of Warcraft\WoW.exe:
corrupted double-linked list: 0x6902d3a8 *** 
======= Backtrace: ========= 
/lib/libc.so.6[0x601e83a4] 
/lib/libc.so.6[0x601ea123] 
/lib/libc.so.6(cfree+0x96)[0x601ea356] 
/usr/lib/nvidia/libGLcore.so.1[0x7cb2cd6a]

City of Heroes locks up with no error message, Vent stays open and looks
like it is working, but all sound (send and receive) stops, again with
no error message. Sometimes I can shut down Vent and restart and it will
work again for a few minutes before crashing, sometimes when I try to
restart it tell me Vent is already running and I have to reboot system.
The OS never locks up, just the programs, and things not running through
Wine are fine.

If I run rpm -qa |grep nvidia I get:

xorg-x11-drv-nvidia-libs-180.29-1.fc10.i386
xorg-x11-drv-nvidia-libs-180.29-1.fc10.x86_64
kmod-nvidia-2.6.27.15-170.2.24.fc10.x86_64-180.29-1.fc10.x86_64
xorg-x11-drv-nvidia-180.29-1.fc10.x86_64
kmod-nvidia-2.6.27.12-170.2.5.fc10.x86_64-180.27-1.fc10.x86_64
kmod-nvidia-180.29-1.fc10.x86_64

I am happy to provide more info, just tell me what and how.

Tricia

For the Wine 'too much RAM' issue, I found two possible fixes:

1)add the mem=3072 (for 3GB) or mem=2048 (For 2GB) flag to your kernel
boot parameters (from
http://appdb.winehq.org/objectManager.php?sClass=version&iId=14154 )

2)set up wine-get and apply a patch (from
http://bugs.winehq.org/show_bug.cgi?id=10778 )

Which is the better choice for a user who needs a stable system?

On Wed, 2009-02-25 at 10:17 -0600, Austin English wrote:
> On Wed, Feb 25, 2009 at 10:11 AM, tparker <tparker at etherstorm.net>
wrote:
> > For the Wine 'too much RAM' issue, I found two possible fixes:
> >
> > 1)add the mem=3072 (for 3GB) or mem=2048 (For 2GB) flag to your kernel
> > boot parameters (from
> > http://appdb.winehq.org/objectManager.php?sClass=version&iId=14154
)
> 
> Easier/quicker.
Okay, I'm going to go with easy/quick since I'm not completely sure this
is the problem yet.

In grub.conf I have two lines that start with kernel, one in this:

title Fedora (2.6.27.15-170.2.24.fc10.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.27.15-170.2.24.fc10.x86_64 ro
root=/dev/VolGroup00/LogVol00 rhgb quiet

and one in this:

title Fedora (2.6.27.12-170.2.5.fc10.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.27.12-170.2.5.fc10.x86_64 ro
root=UUID=1d89eae5-278b-4fed-b1b5-08ffa039ffd8 rhgb quiet

Do I add mem=3072 to the end of both?