[Bug 22103] New: Starcraft II: crashes after "loading" screen with ACCESS_VIOLATION error - wrong video memory size detection

http://bugs.winehq.org/show_bug.cgi?id=22103

Summary: Starcraft II: crashes after "loading" screen with
                    ACCESS_VIOLATION error - wrong video memory size
                    detection
           Product: Wine
           Version: 1.1.41
          Platform: x86-64
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Issue:
- starcraft beta installs correctly
- game updates correctly
- game loads
-- you can see loading screen
-- as soon as loading finishes, game crashes with ACCESS_VIOLATION exception
and opens Blizzard Error Reporter

There's a lot of messages like these while running in console:

fixme:d3d_texture:texture_init Failed to create surface 0x8616658, hr
0x8876017c
err:d3d:resource_init Out of adapter memory
err:d3d9:device_parent_CreateSurface (0x1764d4) CreateSurface failed, returning
0x8876017c

Potential problem:
Wine wrongly detects amount of video card memory

Tested system:
Ubuntu 9.10 "Karmic" 64bit
Wine 1.1.39, 1.1.40, 1.1.41
Nvidia Quadro NVS 140M 512MB

Workaround:
Override detection of memory by setting in registry this key:

HKEY_CURRENT_USER/Software/Wine/Direct3D/VideoMemorySize

to memory amount (eg. 512)

[Bug 22103] Starcraft II: crashes after "loading" screen with ACCESS_VIOLATION error - wrong video memory size detection

http://bugs.winehq.org/show_bug.cgi?id=22103

--- Comment #1 from Norbert   2010-03-21 06:11:30 ---
Created an attachment (id=26945)
 --> (http://bugs.winehq.org/attachment.cgi?id=26945)
Output from console

[Bug 22103] Starcraft II: crashes after "loading" screen with ACCESS_VIOLATION error - wrong video memory size detection

http://bugs.winehq.org/show_bug.cgi?id=22103

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
           Severity|major                       |minor

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Starcraft II: crashes after |Starcraft II: crashes after
                   |"loading" screen with       |"loading" screen
                   |ACCESS_VIOLATION error -    |
                   |wrong video memory size     |
                   |detection                   |

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

elhsmart  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from elhsmart   2010-03-23 01:15:19 ---
Confirm this bug. Expected it while try to star Starcraft 2 on Dell Vostro V13
with integrated Intel GMA4500 Graphics.

As hotfix helps this topic: http://forum.winehq.org/viewtopic.php?t=7005
Maybe this is some broken drivers, but after disabling glsl with winetricks
Starcraft start fine.

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

Thodoris Greasidis  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #3 from Thodoris Greasidis   2010-04-06 08:00:28 ---
Confirming with ati catalyst 10.3 (and earlier).

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

Dan Kegel  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |[e-mail]
     Ever Confirmed|0                           |1

--- Comment #4 from Dan Kegel   2010-04-13 15:03:24 ---
On the Nvidia 220 with 1GB of RAM, the message
err:d3d:resource_init Out of adapter memory
happens earlier, even before the game loading screen comes up.

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

--- Comment #5 from Henri Verbeet   2010-04-13 15:16:04 ---
Probably broken card detection. What does it actually detect? (Check with
+d3d,+d3d_caps.)

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

--- Comment #6 from Dan Kegel   2010-04-13 15:39:31 ---
Created an attachment (id=27354)
 --> (http://bugs.winehq.org/attachment.cgi?id=27354)
WINEDEBUG=+d3d,+d3d_caps,+seh wine StarCraft\ II.exe log

Here's a log up to the second out of memory error.
Yes, it looks like you need a CARD_NVIDIA_GEFORCE_GT220.
I think some of them come with 512MB; mine comes with 1GB.
select_card_nvidia_binary should probably guess 512MB.

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

--- Comment #7 from Dan Kegel   2010-04-13 15:57:15 ---
Norbert/elhsmar/Thodorist, can you attach a log made with
  WINEDEBUG=+d3d,+d3d_caps
?

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

--- Comment #8 from Henri Verbeet   2010-04-13 16:24:44 ---
> trace:d3d:InitAdapters Emulating 64MB of texture ram

Yeah, that's not going to be enough for SC2.

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

Roderick Colenbrander  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #9 from Roderick Colenbrander   2010-04-14 08:11:11 ---
A few days ago someone had the same issue in #winehq. It made me write a small
D3D10 gpu detection patch (and I will of course refine the database but haven't
had time for that yet). Or perhaps I should finally finish my NV-CONTROL
patch..

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

--- Comment #10 from Norbert   2010-04-14 18:24:10 ---
Created an attachment (id=27365)
 --> (http://bugs.winehq.org/attachment.cgi?id=27365)
WINEDEBUG=+d3d,+d3d_caps,+seh wine StarCraft\ II.exe log

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

--- Comment #11 from Norbert   2010-04-14 18:25:35 ---
(In reply to comment #10)
> Created an attachment (id=27365)

--> (http://bugs.winehq.org/attachment.cgi?id=27365) [details]
> WINEDEBUG=+d3d,+d3d_caps,+seh wine StarCraft\ II.exe log

Dan, is that what you asked for?

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

--- Comment #12 from Dan Kegel   2010-04-14 18:47:18 ---
Yes.  Your log has the key lines
trace:d3d_caps:IWineD3DImpl_FillGLCaps GL_RENDERER: "Quadro NVS 140M/PCI/SSE2".
trace:d3d_caps:IWineD3DImpl_FillGLCaps GL_VENDOR: "NVIDIA Corporation".
trace:d3d_caps:IWineD3DImpl_FillGLCaps GL_VERSION: "3.0.0 NVIDIA 185.18.36".
...
trace:d3d:InitAdapters Emulating 64MB of texture ram

The card detection in select_card_nvidia_binary() (see
http://www.winehq.org/pipermail/wine-cvs/2010-March/064826.html )
probably needs to be extended to handle your card.  You might even be
able to write that patch yourself, give it a try.

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

--- Comment #13 from Norbert   2010-04-15 18:03:16 ---
(In reply to comment #12)
> Yes.  Your log has the key lines
> trace:d3d_caps:IWineD3DImpl_FillGLCaps GL_RENDERER: "Quadro NVS 140M/PCI/SSE2".
> trace:d3d_caps:IWineD3DImpl_FillGLCaps GL_VENDOR: "NVIDIA Corporation".
> trace:d3d_caps:IWineD3DImpl_FillGLCaps GL_VERSION: "3.0.0 NVIDIA 185.18.36".
> ...
> trace:d3d:InitAdapters Emulating 64MB of texture ram
>
> The card detection in select_card_nvidia_binary() (see
> http://www.winehq.org/pipermail/wine-cvs/2010-March/064826.html )
> probably needs to be extended to handle your card.  You might even be
> able to write that patch yourself, give it a try.

I'll give it a try. Could you point me to some sources which tells how can I
send patches to wine developers? Or should I post it here?

I also need some help with wine sources - in dlls/wined3d/wined3d_private.h I
added my card "CARD_NVIDIA_QUADRO_NVS140M" to wined3d_pci_device enum. But I
don't know which number should I choose to represent this constant - there's no
comment explaining how to pick one. Same thing with entry in
static const struct driver_version_information driver_version_table[] structure
(directx.c). If this values are somehow easily obtainable (e.g. from wikipedia)
I could try to add support for more cards.

I also don't know how much memory should I assing to my card in directx.c. It
has 128MB built-in memory but with shared memory it actually has 512MB. Which
number should I pick - the lower one? This is part of my code in directx.c:

/* Quadro NVS 140M */
        if (strstr(gl_renderer, "Quadro NVS 140M"))
        {
            *vidmem = 128; /* 128-256MB dedicated memory, 512MB with shared */
            return CARD_NVIDIA_QUADRO_NVS140M;
        }

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

--- Comment #14 from Roderick Colenbrander   2010-04-16 01:08:16 ---
For now pick the lower number, it depends a lot on the vendor whether they put
a 128MB or a 256MB model in the laptop.

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

--- Comment #15 from Norbert   2010-04-16 10:51:32 ---
(In reply to comment #14)
> For now pick the lower number, it depends a lot on the vendor whether they put
> a 128MB or a 256MB model in the laptop.

Ok, thanks. But what about identifiers?

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

--- Comment #16 from Roderick Colenbrander   2010-04-16 10:58:48 ---
Just copy a line from the table and put this device id and the right string
(the renderer string). I'll see if I can write some nvidia code soon and add
more cards as well.

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

Xavier Vachon  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #17 from Xavier Vachon  2010-10-21 08:05:17 CDT ---
Does this happen only with particular graphic cards, or this is a bug only in
the beta version of the game? I have a Geforce 8800 GT, and I have never
experienced this issue since I began playing the retail game in August.

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

joaopa  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #18 from joaopa  2011-07-09 23:27:27 CDT ---
still a bug in current wine?

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

Ken Sharp  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |ABANDONED

--- Comment #19 from Ken Sharp  2013-08-04 10:58:07 CDT ---
Three years, no reply.

[Bug 22103] Starcraft II: crashes after "loading" screen

http://bugs.winehq.org/show_bug.cgi?id=22103

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #20 from Austin English  2013-08-08 16:25:51 CDT ---
Closing.