Having long term, critical issues with WoW

[dering]

Hi,

I've been having some problems with WoW for the past month that have just gotten worse and worse.

My Stats:
I'm running Ubuntu 8.10, 2.6.27-7 generic for a kernel
The CPU is a P4 3.0 ghz, sporting 2 GB of RAM
I'm running with a 512 MB GeForce 7600 GS, AGP 8X, w driver 173.14.12
My wine is 1.1.9, as of the time of this writing

My Symptoms:

Ok problems started shortly after upgrading to 8.10. At first I'd occasionally get the dreaded "Error 132" crash from WoW. I did not think much of it at first. A few days pass, and a few updates, including wine, and the problem becomes MUCH more frequent. The 3.0 patch hits and not as if on cue, I would error 132 crash almost always 15 minutes after logging in. It got so bad, that I simply would no longer see a login screen after getting past the launcher, and just immediately 132 crash.

At this point I had had enough. So I started researching causes of the 132 crash. Following some advice, I decided to reinstall WoW. I wiped it out of the .wine folder, grabbed my DVD's and started installing. The install crashed on a 132 error also. It repeatedly crashes in the same place. There's nothing in the terminal output from running this except a "fixme", wondering where the "FrizQuadratta" font is.

So I need some help figuring this one out, because I really don't want to have to rerig a boot option for a windows install to run WoW. Please lemme know what info I can put together to help you diagnose this. I'm tech savvy, but an admitted Linux newb, so please make your diagnostic question easy to follow, so I can give you the best information possible.

Thanks a lot, in advance to all who'll lend a hand!

[Addys]

Are the errors related to memory exhaustion? Have a look at this bug: http://bugs.winehq.org/show_bug.cgi?id=16131

You may also want to try reinstalling video drivers? http://www.nvidia.com/object/unix.html

[dering]

Sorry I forgot to include the crucial info of what exactly I have tried so far...

As for Nvidia drivers, I've used the restricted driver installer of Ubuntu to install everything from 177 and regressed down I think it was 93? All of them came up with the same issue.

My buddy and I then ran winetricks, to see if it was missing dll issue. No dice.

Our next move was going to be trying to reinstall all likely related packages to try and clear out any legacy BS that might be hanging around in a config file somewhere. I've been running Ubuntu since 7.10, so It wouldn't shock me if there was something. We never got that far though.

Addys, thanks for answering. I took a look at that bug report, while I haven't checked it yet, the bug you mention, and the original it duplicates, both reference 64 bit deployments. Just so I'm certain we're on the same page I'm sporting a Pentium 4, which is 32 bit. Dunno if that changes anything, but I'm covering all the bases here.

[Thunderbird]

Most likely this is again a case of lack of virtual memory. Alexandre added a patch to bug 13335 for this (http://bugs.winehq.org/show_bug.cgi?id=13335) against a git version between 1.1.8 and 1.1.9. It should likely fix your issue but it can take a while before it is in Wine because it has some issues which need to be fixed before it can enter Wine.

[dering]

Bad news...

Unfortunately, the virt mem exhaustion theory is a bust. I tried running the installer again, with top running simultaneously so I could monitor it. Unfortunately there never was any significant jump in virt mem usage during or after the crash.

So any other theories, or diagnostics, or outputs I can provide?

[Thunderbird]

I have updated the patch (bug 13335). Really try it. It isn't really that we use all the memory we allocate we reserve a lot and that causes not much to get left for native libs. Though in general you get out of memory issues and so from GL when this happens but I would still recommend to try this patch.