https://bugs.winehq.org/show_bug.cgi?id=53107
Bug ID: 53107 Summary: LUNARiA trial: some effects fail to display with bogus "Failed to allocate system memory" error Product: Wine Version: 7.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs@winehq.org Reporter: fallenguru@protonmail.com Distribution: ---
Created attachment 72543 --> https://bugs.winehq.org/attachment.cgi?id=72543 terminal output, three ways
Trial download page: https://key.visualarts.gr.jp/kinetic/lunaria/#download Trial download direct link: https://sample9.dmm.com/digital/pcgame/vsat_0274/vsat_0274t.zip Trial SHA1: 4c0f3e206406d36e32634e8f56b558b5accf73ce vsat_0274t.zip
It probably needs Japanese locale (LANG=ja_JP.UTF-8) to run.
To make video playback work, I ran StartData/Config.exe and switched the method from WMP to MCI; then transcoded the videos from WMV to WEBM.
Start a new game, then best hold down the left ctrl key to fast-forward. Assuming you can't read Japanese, or at least don't want to read it all, specifying where the error occurs is a bit difficult. I can attach my savegame directory on request, but the upshot is that it shouldn't crash nor throw any other error.
Anyway, WINE doesn't like some animated(?) effects the game tries to display:
010c:err:d3d:wined3d_resource_allocate_sysmem Failed to allocate system memory. 010c:err:d3d:texture_resource_sub_resource_map Failed to prepare location. (Neither RAM nor VRAM are anywhere near capacity.)
Vanilla WINE crashes right after this with an unhandled page fault. Setting WINE_LARGE_ADDRESS_AWARE=1 got me past the first of these effects (that I noticed); for a later one there's a good chance the game itself pops up an error message instead, roughly: "Image file ef_cyberline could not be opened. An error has occurred in the function LockRect. hr 0x8007000e (E_OUTOFMEMORY)". In that case, it continues to run after and just skips the effect.
So I installed DIVK into the prefix and that has been flawless so far, so I thought a bug in WINE's Direct3D implementation might be in play.
Fresh 7.10 prefix (winehq official repo, Ubuntu 18.04).
https://bugs.winehq.org/show_bug.cgi?id=53107
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://sample9.dmm.com/dig | |ital/pcgame/vsat_0274/vsat_ | |0274t.zip Keywords| |download Distribution|--- |Ubuntu
https://bugs.winehq.org/show_bug.cgi?id=53107
--- Comment #1 from Rafał Mużyło galtgendo@o2.pl --- 'Failed to allocate system memory.' might actually mean 'run out of virtual mapping space'. Check VmPeak/VmSize of the process' /proc status file while process is running.
https://bugs.winehq.org/show_bug.cgi?id=53107
--- Comment #2 from fallenguru@protonmail.com --- (In reply to Rafał Mużyło from comment #1)
Thanks for looking at this!
'Failed to allocate system memory.' might actually mean 'run out of virtual mapping space'.
I thought it might. (But then I also thought WINE_LARGE_ADDRESS_AWARE help with that?)
Check VmPeak/VmSize of the process' /proc status file while process is running.
This is a couple of sec after the crash (without WINE_LARGE_ADDRESS_AWARE):
VmPeak: 4154728 kB VmSize: 4154664 kB
For reference, this is after launch, just sitting at the main menu:
VmPeak: 3907360 kB VmSize: 3637476 kB
Wouldn't take much to hit a 4 GB wall. The point is, Windows doesn't, and neither does DXVK.
w/ DXVK, main menu:
VmPeak: 3891012 kB VmSize: 3349860 kB
w/ DXVK, effect playing:
VmPeak: 3946008 kB VmSize: 3945848 kB
w/ DXVK, on the first screen after the effect.
VmPeak: 3946008 kB VmSize: 3716472 kB
https://bugs.winehq.org/show_bug.cgi?id=53107
--- Comment #3 from fallenguru@protonmail.com --- Created attachment 72553 --> https://bugs.winehq.org/attachment.cgi?id=72553 saved game from just before the problem occurs
This is a savegame directory containing a single saved game to help reproducing this; put it in StartData/GameData/.
Load the save, then just click through the next couple of lines. You'll either get a "high speed" effect or it crashes / errors out.
(I included the system.ini with movie playback already set to MCI as well, might save some time setting up.)