[Bug 45045] New: Vampire: The Masquerade Bloodlines, GL_OUT_OF_MEMORY, worked in wine 1.8

[wine-bugs at winehq.org]

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

            Bug ID: 45045
           Summary: Vampire: The Masquerade Bloodlines,  GL_OUT_OF_MEMORY,
                    worked in wine 1.8
           Product: Wine
           Version: 3.6
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: ckoe_ at web.de
      Distribution: ---

Created attachment 61172
  --> https://bugs.winehq.org/attachment.cgi?id=61172
Console outputs and backtraces for different videomemorysize settings.

Hello everybody,

I would like to report a crash of Vampire: The Masquerade Bloodlines (VTMB)
upon or shortly after loading of a saved game just after a fresh start of the
main game and/or area transition. It worked fine with wine 1.6 (debian jessie)
and the wine 1.8 from debian 9 (stretch, stable). It crashes with wine 3.0 and
wine 3.6 as detailed below.

The crash might be related to https://bugs.winehq.org/show_bug.cgi?id=42732 and
it has superficial similarities to
https://bugs.winehq.org/show_bug.cgi?id=24701   but because it worked for me
without problems in the earlier wine versions mentioned above I believe 24701
can be ruled out and I would like to file a new bug report explicitely. Please
feel free to eventually mark as duplicate as appropriate. I have some hope that
it might help people with the same problem anyway if they can find it.

The VTMB in question is the version distributed by GOG including the Unoffical
Patch version 9.7 by wesp5 as distributed by GOG (plus some additional
textures). The OS is debian 9 (stretch, stable) on a Haswell with IGP HD4400,
before upgrading I ran it on debian jessie (8, old-stable) on the same
hardware.

Again: No problems were observed with wine 1.6 and wine 1.8.

With wine 3.0 and wine 3.6 (I will only report/attach wine 3.6 details below) I
now observe a memory usage related crash upon (usually) loading of a saved game
and/or area transition depending on "winetricks videomemorysize=". The game was
newly started each time, i.e. it does not crash after hours of playing but
basically immediately.

I see on the console 
0038:err:d3d:wined3d_debug_callback 0x1ba070: "GL_OUT_OF_MEMORY in ...
before it crashes. I attached the console outputs and backtraces for various 
videomemorysize settings, i.e. default, 512, 1024, 2048. They do not make a
noticeable difference.

I then set LARGE_ADDRESS_AWARE as suggested in 42732 on vampire.exe. With this
modified binary I could not observe any problems when loading saves or doing
area transitions, but I tested it only for a few minutes. Still, this is an
obvious change.

So, in summary some change in wine after wine 1.8 might have broken that game
by somehow changing the memory layout.

Please let me know if I should gather any additional information.

Best Regards

Christof

P.S.: I tried to submit the same bug previously but it somehow never showed up
in the bug list. Not sure what happened.

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