[Bug 41156] New: World of Warcraft 3.3.5 crashes with the " video memory is run out" error
https://bugs.winehq.org/show_bug.cgi?id=41156 Bug ID: 41156 Summary: World of Warcraft 3.3.5 crashes with the "video memory is run out" error Product: Wine Version: 1.9.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mad_sam(a)bk.ru Distribution: --- My configuration: CPU: AMD A8-5557M VIDEO: AMD HD8750M (2G video memory) amd AMD HD8550G (512Mb video memory) RAM: 8GB Video driver: Radeon Game: World of Warcraft 3.3.5 Game crashes after long playing in new locations (Northrend), more often in raid dungeons on 25 people. Wine output: radeon: mmap failed, errno: 12 radeon: mmap failed, errno: 12 radeon: mmap failed, errno: 12 ...lot of spam radeon: mmap failed, errno: 12 Game client error: The instruction at "0x7D50FF49" referenced memory at "0x00000034". The memory could not be "read". It was tested on two computers. And tested in Windows 7 and Windows 10, no errors been found, so i guess it is a wine bug (or Radeon driver). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41156 Alex <mad_sam(a)bk.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41156 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41156 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #1 from winetest(a)luukku.com --- How do you play such an old version of WOW? How is it possible? The current latest version is 7.1. How do you play it so that game doesn't upgrade itself? Which gpu you use for gaming? I am not sure if wine sees your gpus correctly. Were the test done in windws using same hardware? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41156 --- Comment #2 from Alex <mad_sam(a)bk.ru> --- (In reply to winetest from comment #1)
How do you play such an old version of WOW? How is it possible? The current latest version is 7.1. How do you play it so that game doesn't upgrade itself?
I'm "old" wow player, and I'm playing only wow 1.12, 2.4.3 and 3.3.5. It possible only on private servers.
Which gpu you use for gaming? I am not sure if wine sees your gpus correctly.
AMD HD8550G only works in linux, because HD8750M doesn't have video output.
Were the test done in windws using same hardware?
Sure. Now i use Gentoo and don't have this problem anymore (crashes with the radeon: mmap failed, errno: 12). My mesa compiled with next use-flags: classic d3d9 dri3 egl gallium gbm gles2 llvm nettle nptl vaapi xa -bindist -debug -gcrypt -gles1 -libressl -opencl -openmax -openssl -osmesa -pax_kernel -pic (-selinux) -valgrind -vdpau -vulkan -wayland -xvmc -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41156 --- Comment #3 from winetest(a)luukku.com ---
Now i use Gentoo and don't have this problem anymore (crashes with the radeon: mmap failed, errno: 12). My mesa compiled with next use-flags: classic d3d9 dri3 egl gallium gbm gles2 llvm nettle nptl vaapi xa -bindist -debug -gcrypt -gles1 -libressl -opencl -openmax -openssl -osmesa -pax_kernel -pic (-selinux) -valgrind -vdpau -vulkan -wayland -xvmc
You mean you can't anymore reproduce the issue? This means either it got fixed in wine or was never a wine probelm to start with. If you can't reproduce the issue and there are no others complaining this then this bug should be closed. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41156 Alex <mad_sam(a)bk.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #4 from Alex <mad_sam(a)bk.ru> --- In Arch Linux bugtracker. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=41156 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #5 from Austin English <austinenglish(a)gmail.com> --- Closing. -- 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.
participants (1)
-
wine-bugs＠winehq.org