http://bugs.winehq.org/show_bug.cgi?id=59571 --- Comment #14 from Antoine Le Gonidec <accounts.winehq@vv221.fr> --- About WINEARCH=win32, it is mostly due to lack of time to test WoW64, both old and new. When I finally started hearing about it again, it was because distributions switching to the new WoW64 mode made many games unplayable, so of course it did not lead me to be an early adopter ;) Then there is the problem of twice the storage space being required to generate the WINE prefix, while half of that is never going to be used if only 32-bit software is going to be run (based on my experience with the old mode, I don’t know if it is still the case with the new one). Another problem with my use case is that many winetricks calls take twice as long to run, sometimes with twice as much user interaction, because 64-bit builds of libraries are being installed despite having no use in that specific prefix. As I said above, I am going to give a try to a current build with WoW64 (new variant) anyway. No matter if I am going to use it or not, it is worth knowing if it has a positive effect on this crash. --- I find it strange that this problem would be memory related, especially as the crashes I got on maps loading (#54833 ?) only happened with the base game alone, not with the expansions. And I expect the expansions to eat a bit more memory, due to having more content. My workaround for this crash on maps loading, workaround that has no effect on the current crash, is to restore a previous version of the game binary. I did not get that crash with any GOG.com builds before the most current one, where they did change something to the game binary without documenting it. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.