http://bugs.winehq.org/show_bug.cgi?id=58927
Bug ID: 58927 Summary: Battlefield 2 crashes on Wine at the loading of a mission Product: Wine Version: 10.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: scottkidman@protonmail.com Distribution: ---
Created attachment 79615 --> http://bugs.winehq.org/attachment.cgi?id=79615 Battlefield 2 Crash
Despite the report here: https://appdb.winehq.org/objectManager.php?sClass=version&iId=3438, which marked Battlefield 2 as platinum, Battlefield 2 crashes before the mission starts.
I am running Linux Mint 22.2 with native drivers. My computer is an AMD Phenom II X3 B75 with 4GB DDR3 RAM. The Wine version is 10.18 Development.
This happened both in Battlefield 2 original and Battlefield 2 Special Forces, where the loading is complete and the mission starts.
I would add that the Wine version tested by the tester in the provided link was using 10.16 Staging, and that the test was recent.
I have included the log, and I apologise beforehand if it doesn't meet with criteria. If you can tell me how to test, I would be grateful.
http://bugs.winehq.org/show_bug.cgi?id=58927
Scott Kidman scottkidman@protonmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Battlefield 2 crashes on |Battlefield 2 crashes on |Wine at the loading of a |Wine after the loading and |mission |start of a mission
http://bugs.winehq.org/show_bug.cgi?id=58927
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #1 from joaopa jeremielapuree@yahoo.fr --- Does the bug occur with the demo https://community.pcgamingwiki.com/files/file/1108-battlefield-2-updated-dem...
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #2 from Scott Kidman scottkidman@protonmail.com --- Created attachment 79631 --> http://bugs.winehq.org/attachment.cgi?id=79631 Battlefield 2 Demo Log
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #3 from Scott Kidman scottkidman@protonmail.com --- (In reply to joaopa from comment #1)
Does the bug occur with the demo https://community.pcgamingwiki.com/files/file/1108-battlefield-2-updated- demo/
Yes.
Log attached.
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #4 from joaopa jeremielapuree@yahoo.fr --- For me the demo crashes too. But if I install a native d3dx9 dll then the game works well.
Can you try that for both demo and retail game ?(easy way: install winetricks and then winetricks d3dx9 should do the trick)
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #5 from Scott Kidman scottkidman@protonmail.com --- I did that, but the problem is still there.
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #6 from Scott Kidman scottkidman@protonmail.com --- (In reply to Scott Kidman from comment #5)
I did that, but the problem is still there.
Here's what I have installed on the prefix for testing using Winetricks:
- d3dx9 - directshow - quicktime76 - vcrun2005 - wmp9
It's a 32-bit prefix.
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #7 from Scott Kidman scottkidman@protonmail.com --- I should add that they were not installed for testing Battlefield 2. There were used for something else, other games for example.
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #8 from Scott Kidman scottkidman@protonmail.com --- (In reply to joaopa from comment #4)
For me the demo crashes too. But if I install a native d3dx9 dll then the game works well.
Can you try that for both demo and retail game ?(easy way: install winetricks and then winetricks d3dx9 should do the trick)
Should I rewipe my Linux Mint installation and start anew?
http://bugs.winehq.org/show_bug.cgi?id=58927
LingM lingm+winebz@posteo.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lingm+winebz@posteo.org
--- Comment #9 from LingM lingm+winebz@posteo.org --- Gods no. Everything winetricks installs is installed into a prefix. You can just create a new, clean prefix to test stuff. If you haven't specified which prefix to use, yours should be in ~/.wine. Rename that folder and it will automatically create a clean one.
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #10 from Scott Kidman scottkidman@protonmail.com --- (In reply to LingM from comment #9)
Gods no. Everything winetricks installs is installed into a prefix. You can just create a new, clean prefix to test stuff. If you haven't specified which prefix to use, yours should be in ~/.wine. Rename that folder and it will automatically create a clean one.
Well, the problem is there. Not complaining as it's just a game, and I have many.
OK, I'll watch this thread for more.
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #11 from joaopa jeremielapuree@yahoo.fr --- in a terminal, you have to do the following only : be sure that you are in your home directory, then: mv .wine .wine.bak (to avoid to lose all you already installed programs) then reinstall battlefield with the latest vanilla wine (currently it is wine 10.18). without dll overrides you will get a crash. After installing d3dx9 (with winetricks) crash will disappear.
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #12 from Scott Kidman scottkidman@protonmail.com --- I just made another prefix, and this time, it had nothing but d3dx9.
I called it .bf2.
Is this the same effect?
Then I installed BF2 Full and the same happens.
I kid you not.
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #13 from joaopa jeremielapuree@yahoo.fr --- did you use the latest vanilla wine?
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #14 from Scott Kidman scottkidman@protonmail.com --- If you're talking about 10.18, yes.
I only use the latest Wine.
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #15 from joaopa jeremielapuree@yahoo.fr --- I meant the devel verson of wine, not staging.
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #16 from Scott Kidman scottkidman@protonmail.com --- I know, I use that all the time, Devel, not Staging, and not Stable.
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #17 from Scott Kidman scottkidman@protonmail.com --- Listen, I'm going to wipe the drive.
Why don't we wait until then and then I'll report back to you after I do it when I reinstall my games and retest Battlefield 2?
http://bugs.winehq.org/show_bug.cgi?id=58927
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #18 from Zeb Figura z.figura12@gmail.com --- (In reply to Scott Kidman from comment #17)
Listen, I'm going to wipe the drive.
Why don't we wait until then and then I'll report back to you after I do it when I reinstall my games and retest Battlefield 2?
There's really nothing that's going to solve.
The problem is probably not due to d3dx, but rather:
0158:err:d3d:resource_init Out of adapter memory.
That's probably VA exhaustion.
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #19 from LingM lingm+winebz@posteo.org --- Dusted off my retail DVD. It installed Battlefield 2 v1.1.2551.0. Didn't install any further patches. Clean prefix without anything from winetricks. Game loads fine into single player mode.
I'm on an Arch-derivative which enables the new wow64 mode though. If it's really VA exhaustion, the wow64 might be what's helping me.
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #20 from Scott Kidman scottkidman@protonmail.com --- (In reply to Zeb Figura from comment #18)
(In reply to Scott Kidman from comment #17)
Listen, I'm going to wipe the drive.
Why don't we wait until then and then I'll report back to you after I do it when I reinstall my games and retest Battlefield 2?
There's really nothing that's going to solve.
The problem is probably not due to d3dx, but rather:
0158:err:d3d:resource_init Out of adapter memory.
That's probably VA exhaustion.
What's VA exhaustion?
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #21 from Rafał Mużyło galtgendo@o2.pl --- (In reply to Scott Kidman from comment #20)
What's VA exhaustion?
Virtual address space.
If you were to open something like top, you'd a 'Virt' field besides the process.
For 32bit apps, there's 4GB limit for that value, once the app reaches that limit, new memory allocations fail, leading to various odd failures, sometimes even crashes.
In /proc you'll see that value for a process in the status file under VmSize.
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #22 from Scott Kidman scottkidman@protonmail.com --- So the problem's on my end?
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #23 from Rafał Mużyło galtgendo@o2.pl --- (In reply to Scott Kidman from comment #22)
So the problem's on my end?
Well, yes and no.
If all the RAM you have is 4GB, that's a bit low, yet it depends.
Some games in wine have excessively high VM consumption and (next to) nothing can be done about it (there is - for example - a case where winegstreamer can kill a game with vm exhaustion despite the game using very little memory (well, I haven't rechecked that bug (or two) in a couple years, but I don't recall any changes there since, major enough to make a difference)). In other cases though the excessive consumption is a genuine bug and can be fixed.
Which case we're dealing with here is still uncertain.
http://bugs.winehq.org/show_bug.cgi?id=58927
--- Comment #24 from Scott Kidman scottkidman@protonmail.com --- Created attachment 79664 --> http://bugs.winehq.org/attachment.cgi?id=79664 Exception Report
I was able to save this. I can't believe I didn't think to do this!
Sorry.