Das Forum

Running World of Tanks in 64bit wine

Autor Antworten
der Papst Thursday 24 April 2014 at 16:56
der PapstAnonymous

Till WOT 9.0, the game was only a little bit unstable on Linux (rare crashes to desktop)
With 9.0, it became much worse.

Many users in the official forums suspects, the crashes are caused by running out of memory - seems legit to me since it explains many things i have noticed (1).
Some users also report crashes exactly when the game reaches 2GB.
Since windows-users have similar problems, i guess it is caused by bugs (memory leaks?) which will hopefully be fixed in the next hotfix.
But the need of resources of v9.0 has clearly increased and mods make the situation worse.

I read, applications run on 32bit windows can only use 2GB.
What is the easiest way to run the game in 64bit, since the installation script installs it in 32bit but also installs additional software and winetricks - so i can't just install it in a 64bit virtual drive.

(1) When I die before the round ends, the probability to crash is lower...
Mods which increase the needed ressources also increase the rate of crashes.
petch Thursday 24 April 2014 at 20:35


The script installs Internet Explorer 8, which doesn't seem to be installable in a 64bit Wine virtual drive...
der Papst Thursday 24 April 2014 at 21:39
der PapstAnonymous

What can i do in that case?
Other Browser?
Internet Explorer 64bit?

I just played while watching KSysGuard...
1st round ~1,4GB, 2nd round ~1,8GB, 3rd round ~1,9GB -> crash do desktop at the end of round 3...

Btw: Why 2 GB?
i thought a 32bit-System is able to address 3,7GB?
petch Thursday 24 April 2014 at 21:47

Wine expects the user address space to end at 0xC0000000 so I would be expecting a 3GB limit...

No idea about a solution, just pointing out that modifying the script to create a 64bit virtual drive won't be sufficient.
petch Sunday 27 April 2014 at 12:28

Mmmh it seems the 0x80000000 ~ 0xC0000000 address space is also reserved:
der Papst Sunday 1 June 2014 at 20:30
der PapstAnonymous

What's the best way to find the reason for the crash to desktop?
Or, at least to determine if the game crashes because of running out of memory...

I also noticed (when i tried it on win7), that the game needs on windows nearly half of the memory, which is really strange because i played it on win7 on maximum graphics which i can't do on Linux because of low fps, so i set it to ~medium.