[Bug 42145] New: Guild Wars 2 crashes on some configurations

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=42145

            Bug ID: 42145
           Summary: Guild Wars 2 crashes on some configurations
           Product: Wine
           Version: 2.0-rc3
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: me at aaronopfer.com
      Distribution: ---

Created attachment 56713
  --> https://bugs.winehq.org/attachment.cgi?id=56713
GW2-generated crash log

Guild Wars 2 crashes on my laptop psuedorandomly while playing the game. I
managed to create a reproduceable version of the crash: all I have to do is
toggle the visibility of my helmet slot in my Hero's Equipment panel (a feature
designed for those who don't want ugly helmets covering their character's
faces) and the game will reliably crash.

I am using 64bit wine. I reproduced the crash initially in 2.0.0-rc3-staging,
then in 2.0.0-rc3, and then again in 1.7.35. I haven't tested any other
versions.

The crash does NOT occur on my desktop despite similar wine versions and
configurations. The main difference between the laptop and the desktop is that
the desktop uses the proprietary nvidia blob on a GTX 780, and the laptop uses
integrated intel HD 5500 graphics. The laptop and desktop are running the
debian 4.8.0 kernel. 

As an aside, another laptop I have running debian is using a nvidia mobile GPU
(don't remember the model) via bumblebee and it also has no problems with
crashing in GW2.

I have some modest debugging skills: poking around in a debugger shows that the
crash occurs in what appears to be blitting code (the Gw2-64.exe binary makes
string references to "ImgBlt.cpp" in the area). The fault instruction is a rep
movsb. During normal operation the rep movsb's operands are in low memory
ranges (mask 0xFFFFFFFF), but when it crashes one operand is
(0x0222000000000000) which is not valid memory and causes a crash.

I do not have a Windows machine so I do not know if Windows has the same crash;
I presume not.

I have attached the Arenanet.log file which contains some information about
what went wrong. It may contain multiple crashes; I'm not very familiar with
these GW2-specific crashlogs so I'm not sure. These are made by GW2's built-in
crash logger. If anyone wants another crash log format you'll have to tell me
how to disable GW2's built-in one.

If anyone wants me to do any specific debug actions or logs I'll be happy to
try them.

-- 
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.