https://bugs.winehq.org/show_bug.cgi?id=46371
Bug ID: 46371 Summary: FFXI + Ashita random crash ingame Product: Wine-staging Version: 4.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: winehq@foreversmall.com CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Created attachment 63113 --> https://bugs.winehq.org/attachment.cgi?id=63113 Crash log from Intel GPU
There appears to be some issue with wined3d in Wine 4.0rc3. I haven't been able to nail down the pattern yet but it seems like when a lot of geometry is being loaded. For example, zoning into a new area, or entering a cut scene can cause a crash but it isn't every time. Unsure when this was introduced as I wasn't able to login until bug 46263 was resolved. I have two separate crash reports one with a Intel driver and the other with Nvidia proprietary driver. Both crash in similar circumstances.
https://bugs.winehq.org/show_bug.cgi?id=46371
--- Comment #1 from Algaris winehq@foreversmall.com --- Created attachment 63114 --> https://bugs.winehq.org/attachment.cgi?id=63114 Crash log from Nvidia GPU
https://bugs.winehq.org/show_bug.cgi?id=46371
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal Product|Wine-staging |Wine Component|-unknown |-unknown
--- Comment #2 from Matteo Bruni matteo.mystral@gmail.com --- Can you please attach the whole, plain terminal output, as in https://wiki.winehq.org/FAQ#get_log?
I suspect the game is running out of virtual memory.
https://bugs.winehq.org/show_bug.cgi?id=46371
--- Comment #3 from Algaris winehq@foreversmall.com --- Created attachment 63287 --> https://bugs.winehq.org/attachment.cgi?id=63287 FFXI/Ashita crash report
Here is the updated crash log with full terminal output. Please let me know if you need anything else.
https://bugs.winehq.org/show_bug.cgi?id=46371
--- Comment #4 from Algaris winehq@foreversmall.com --- Looks like there have been a few other reports of this same problem in the AppDB page. https://appdb.winehq.org/objectManager.php?sClass=version&iId=2739
https://bugs.winehq.org/show_bug.cgi?id=46371
--- Comment #5 from Matteo Bruni matteo.mystral@gmail.com --- Interesting bit from the log:
0030:err:d3d8:d3d8_device_upload_sysmem_vertex_buffers Failed to update buffer.
Does this still happen with current Wine? If so, can you please attach a d3d8,d3d trace?
https://bugs.winehq.org/show_bug.cgi?id=46371
--- Comment #6 from Algaris winehq@foreversmall.com --- Created attachment 63410 --> https://bugs.winehq.org/attachment.cgi?id=63410 ffxi d3d d3d8 trace
The log is entirely too large to attach directly. Here's a link to the updated trace with wine4.0 rc7. I'm unable to use wine stable 4.0 because I need the patch from Bug 46263 to get in game. Is there a wine-staging build of wine 4.0 stable?
https://bugs.winehq.org/show_bug.cgi?id=46371
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |emegas@vecanti.org
--- Comment #7 from Matteo Bruni matteo.mystral@gmail.com --- *** Bug 46556 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=46371
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW
--- Comment #8 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Algaris from comment #6)
Created attachment 63410 [details] ffxi d3d d3d8 trace
The log is entirely too large to attach directly. Here's a link to the updated trace with wine4.0 rc7. I'm unable to use wine stable 4.0 because I need the patch from Bug 46263 to get in game. Is there a wine-staging build of wine 4.0 stable?
Thank you for the log, I see the issue.
The game sets a SYSMEM buffer as stream source 1 and makes a few draws with it. At some point it stops using the buffer (the following draws only use stream source 0) but it keeps it bound there. That currently means we unnecessarily upload the buffer in every following draw. That's not great but also not critical, until the game releases the buffer and we crash at the next draw while trying to upload the buffer again.
I'll write a patch.
https://bugs.winehq.org/show_bug.cgi?id=46371
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |75b7ff60562880b6e7b646a8fa8 | |4486670162d00 Component|-unknown |directx-d3d
https://bugs.winehq.org/show_bug.cgi?id=46371
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
https://bugs.winehq.org/show_bug.cgi?id=46371
--- Comment #9 from Algaris winehq@foreversmall.com --- (In reply to Matteo Bruni from comment #8)
(In reply to Algaris from comment #6)
Created attachment 63410 [details] ffxi d3d d3d8 trace
The log is entirely too large to attach directly. Here's a link to the updated trace with wine4.0 rc7. I'm unable to use wine stable 4.0 because I need the patch from Bug 46263 to get in game. Is there a wine-staging build of wine 4.0 stable?
Thank you for the log, I see the issue.
The game sets a SYSMEM buffer as stream source 1 and makes a few draws with it. At some point it stops using the buffer (the following draws only use stream source 0) but it keeps it bound there. That currently means we unnecessarily upload the buffer in every following draw. That's not great but also not critical, until the game releases the buffer and we crash at the next draw while trying to upload the buffer again.
I'll write a patch.
Thanks for all your effort!
https://bugs.winehq.org/show_bug.cgi?id=46371
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |873178c03a56eca4d818369386b | |0be6ba01b08c4 Resolution|--- |FIXED Status|NEW |RESOLVED
--- Comment #10 from Matteo Bruni matteo.mystral@gmail.com --- This bug should be fixed by 873178c03a56eca4d818369386b0be6ba01b08c4 which is in Wine 4.3. Please retest and reopen if not fixed.
https://bugs.winehq.org/show_bug.cgi?id=46371
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #11 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 4.4.
https://bugs.winehq.org/show_bug.cgi?id=46371
--- Comment #12 from Algaris winehq@foreversmall.com --- I just wanted to confirm this issue seems to be fixed. I've tested it several different ways and I'm unable to reproduce the same behavior and there are no errors during play.
However I did want to report 2 errors after I exited the game below. They didn't appear to have any noticeable effect and the game exited cleanly. I still wanted to make you aware of it though.
0046:err:d3d:wined3d_device_decref Device released with resources still bound. 0046:err:d3d:wined3d_device_decref Leftover resource 0x18db2270 with type WINED3D_RTYPE_BUFFER (0x1).
https://bugs.winehq.org/show_bug.cgi?id=46371
Michael Stefaniuc mstefani@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |4.0.x
https://bugs.winehq.org/show_bug.cgi?id=46371
Michael Stefaniuc mstefani@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|4.0.x |---
--- Comment #13 from Michael Stefaniuc mstefani@winehq.org --- Removing the 4.0.x milestone from bug fixes included in 4.0.2.
-
wine-bugs＠winehq.org