http://bugs.winehq.org/show_bug.cgi?id=34549
Bug #: 34549 Summary: PAYDAY 2 crashes on level completion Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: jeff@deseret-tech.com Classification: Unclassified
Created attachment 45996 --> http://bugs.winehq.org/attachment.cgi?id=45996 pd2 crash log
After completing a couple of levels, PAYDAY 2 will crash on the level success screen and the player will be deprived of earned loot and experience.
This seems to be related to video memory. There are other indications of starved video memory while in-game, like shiny, textureless person models.
I'm using nvidia GTX 670 on 325.15 and Linux 3.11.1, wine 1.7.2 and 8b933495fb4b9a. This issue seems to occur much less frequently with ATI cards.
My log on crash with WINEDEBUG=-d3d (because the game spams d3d errors throughout play) is attached.
http://bugs.winehq.org/show_bug.cgi?id=34549
--- Comment #1 from Jeff Cook jeff@deseret-tech.com 2013-09-19 02:25:22 CDT --- For reference, here is an example of the console output without the d3d debug channel suppressed. This line is spammed continuously throughout gameplay.
fixme:d3d:swapchain_gl_present Render-to-fbo with WINED3D_SWAP_EFFECT_FLIP
http://bugs.winehq.org/show_bug.cgi?id=34549
--- Comment #2 from Jeff Cook jeff@deseret-tech.com 2013-09-19 02:36:51 CDT --- Created attachment 45997 --> http://bugs.winehq.org/attachment.cgi?id=45997 PAYDAY 2 d3d spammed output
Posted too early on the last one. This output is also spammed once a game is entered, and is spammed through the entirety of gameplay without suppression of d3d debug channel.
http://bugs.winehq.org/show_bug.cgi?id=34549
Jeff Cook jeff@deseret-tech.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #45996|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=34549
Jeff Cook jeff@deseret-tech.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #45997|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=34549
--- Comment #3 from Jeff Cook jeff@deseret-tech.com 2013-10-01 23:05:14 CDT --- Still occurring with db86409db663, Linux 3.11.2, and nvidia 325.15.
http://bugs.winehq.org/show_bug.cgi?id=34549
Yuri Shishenko yurishish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |yurishish@gmail.com
--- Comment #4 from Yuri Shishenko yurishish@gmail.com 2013-11-14 13:22:57 CST --- https://bugs.winehq.org/show_bug.cgi?id=33603 This bug may be related. At least proposed patch fixes this problem.
https://bugs.winehq.org/show_bug.cgi?id=34549
--- Comment #5 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.37 or newer) wine? If so, please attach the terminal output in 1.7.37 (see http://wiki.winehq.org/FAQ#get_log).
https://bugs.winehq.org/show_bug.cgi?id=34549
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man@post.com
--- Comment #6 from super_man@post.com --- Please fill the version field with : wine 1.7.2 since that is the reported version.
Does this still occur? We are currently at 1.7.55.
https://bugs.winehq.org/show_bug.cgi?id=34549
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
https://bugs.winehq.org/show_bug.cgi?id=34549
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Hardware|x86 |x86-64 Version|unspecified |1.7.2 Resolution|--- |ABANDONED
--- Comment #7 from Anastasius Focht focht@gmx.net --- Hello folks,
no further response from OP, resolving 'ABANDONED'.
Unrelated to actual problem but preventing proper symbol lookup: bug 39570
--- snip --- ... fixme:dbghelp:validate_addr64 Unsupported address fffffffff75f0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff6d10000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff75e0000 err:dbghelp:pe_load_dbg_file Couldn't find .DBG file "dll\pdh.dbg" ("") fixme:dbghelp:validate_addr64 Unsupported address fffffffff6c20000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff7320000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff6f50000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff6f20000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff6860000 ... --- snip ---
Regards
https://bugs.winehq.org/show_bug.cgi?id=34549
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org