Starcraft II crash seconds into multiplayer game. 1.9.14 sta

[RlndVt]

When I play Starcraft II can queue up for a game but then moments into the match SC2 crashes. This usually happens two seconds in, but has also happened after ten seconds or so.

This however does not seem to happen consistently. Sometimes the game runs flawlessly, usually after a wine wipe and reinstall, but that doesn't always fix it.

I'm running wine 1.9.14 staging on kubuntu 16.04 with CSMT enabled.

Can anyone help me? Do you need more info from me?

Some things I thought might be interesting for the wine log:

debug.txt.zip

Debug log file.

(3.78 KiB) Downloaded 112 times

This line had like a thousand repititions:

Code: Select all

fixme:keyboard:X11DRV_MapVirtualKeyEx keyboard layout 0x4090409 is not supported

I believe this also happened just before the crash:

Code: Select all

err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded

[Bob Wya]

If it's a CSMT-specific bug and it's reproduce-able then I'd definitely file a bug, on the WineHQ Bugzilla, for it.

You might want to launch the game with following debug channels enabled:

Code: Select all

export WINEDEBUG=+d3d_shader,+d3d

All the CSMT main patches appear to mainly apply in:

Code: Select all

/dlls/wined3d/*

so those 2 channels should pick up if anything useful is output in the console stream.

It might be worth doing separate runs both with and without the CSMT patchset enabled.

Bob

[RlndVt]

This morning I wanted to write about how this didn't have anything to do with csmt. But before I did, I disabled and tried again.

The game worked flawlessly! I played the entire morning without a hitch.

BUT, this afternoon I tried playing a game again, and regardless of switching between csmt on or off or switching to 1.9.13, nothing seemed to help.

I'm now inclined to submit a bug report bot don't know how to move forwards. The game is installed using playonlinux, and I wouldn't know how to include the parameters you mentioned.

[andrew.smart]

Hi, I encounter the same issue a few seconds into the lobby, but only in a 64 bit wine. I've never had the issue with 32 bit wine. My 32/64 bit wineprefixes are the same I think (same dll overrides/settings).

Here is a snip of the game's crash log (~/documents/StarCraft II/GameLogs/2016-12-15 00.21.08 crunchbang B48645 Crash/2016-12-15 00.21.08 crunchbang B48645 Crash.txt):

Code: Select all

====================================================================================================
StarCraft II (B48645)

Executable              D:\StarCraft II\Versions\Base48645\SC2_x64.exe
<Parameters>            -sso=1 -launch -uid s2_enus
Parent Executable       \Device\HarddiskVolume2\StarCraft II\Support64\SC2Switcher_x64.exe
Grandparent Executable  \Device\HarddiskVolume1\Program Files (x86)\Battle.net\Battle.net.8180\Battle.net.exe
LocalTime               2016-12-15 00:21:10.055
<ComputerUser>          crunchbang
<ComputerName>          crunchbang
<Exe.Architecture>      x86_64
<Version>               3.9.0.48645
<DataBuild>             B48645
<CodeBranch>            branches/SC2.3.9
<CodeRevision>          352248
<Locale.Assets>         enUS
<Locale.Data>           enUS
<Locale.Install>        enUS
<AccountCountry>        USA
<AgentVersion>          2.8.1.5332
<Inspector.ProjectId>   3
<Inspector.IssueType>   Exception
<Inspector.BuildNumber> B48645 (SC2.3.9)
<Inspector.Branch>      branches/SC2.3.9
<Inspector.Field2>      SC2 Bug Staging
<Inspector.Priority>    2 - High
<Inspector.Summary>     [WINE] ACCESS_VIOLATION reading from 0x00007F5BB83376CC Context EIP:00000001400F36A5
<ErrorType>             ACCESS_VIOLATION (0xC0000005)
<GetLastError>          0
<Application>           StarCraft II
<InstanceID>            0
====================================================================================================
<Inspector.Assertion:>

ACCESS_VIOLATION
reading from 0x00007F5BB83376CC
Context EIP:00000001400F36A5


<:Inspector.Assertion>
====================================================================================================

And my wine versioning:

Code: Select all

$ apt-cache policy wine-development
wine-development:
  Installed: 1.9.14-1~bpo8+1
  Candidate: 1.9.22-1~bpo8+1
  Version table:
     1.9.22-1~bpo8+1 0
        100 http://http.debian.net/debian/ jessie-backports/main amd64 Packages
 *** 1.9.14-1~bpo8+1 0
        100 /var/lib/dpkg/status
$ apt-cache policy wine64-development
wine64-development:
  Installed: 1.9.14-1~bpo8+1
  Candidate: 1.9.22-1~bpo8+1
  Version table:
     1.9.22-1~bpo8+1 0
        100 http://http.debian.net/debian/ jessie-backports/main amd64 Packages
 *** 1.9.14-1~bpo8+1 0
        100 /var/lib/dpkg/status

I'll try updating and see if it works on 64 bit wine. But just letting you know it works for me on 32 bit wine. I have no idea what CSMT means.

[andrew.smart]

Ok, I tried just now with wine64-development 1.9.24-1~bpo8+1 and that was still affected. So... use 32-bit wine as workaround.

[Bob Wya]

...
I have no idea what CSMT means.

See Github: wine-compholio/wine-staging CSMT ...

Bob