[Bug 39724] New: GL_INVALID_OPERATION in glCopyTexImage2D(read buffer); (0x502) from glGenFramebuffers()
https://bugs.winehq.org/show_bug.cgi?id=39724
Bug ID: 39724 Summary: GL_INVALID_OPERATION in glCopyTexImage2D(read buffer); (0x502) from glGenFramebuffers() Product: Wine Version: 1.7.55 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: directx-d3d Assignee: wine-bugs@winehq.org Reporter: backbone@backbone.ws Distribution: ---
Created attachment 52977 --> https://bugs.winehq.org/attachment.cgi?id=52977 Crash log №1
After several minutes of playing the game crashes. Previous (Underground) and next (Most Wanted) games works fine. I have tested installations from 2 different sources and have the same result. Log files in the attachments.
https://bugs.winehq.org/show_bug.cgi?id=39724
--- Comment #1 from Kolan Sh backbone@backbone.ws --- Created attachment 52978 --> https://bugs.winehq.org/attachment.cgi?id=52978 Crash log №2
https://bugs.winehq.org/show_bug.cgi?id=39724
--- Comment #2 from Kolan Sh backbone@backbone.ws --- Created attachment 52979 --> https://bugs.winehq.org/attachment.cgi?id=52979 Crash log №3
https://bugs.winehq.org/show_bug.cgi?id=39724
Kolan Sh backbone@backbone.ws changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Gentoo
https://bugs.winehq.org/show_bug.cgi?id=39724
Kolan Sh backbone@backbone.ws changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |backbone@backbone.ws
https://bugs.winehq.org/show_bug.cgi?id=39724
Kolan Sh backbone@backbone.ws changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|GL_INVALID_OPERATION in |Need For Speed Underground |glCopyTexImage2D(read |2: GL_INVALID_OPERATION in |buffer); (0x502) from |glCopyTexImage2D(read |glGenFramebuffers() |buffer); (0x502) from | |glGenFramebuffers()
https://bugs.winehq.org/show_bug.cgi?id=39724
Kolan Sh backbone@backbone.ws changed:
What |Removed |Added ---------------------------------------------------------------------------- Alias| |nfsu2_gl_invalid
https://bugs.winehq.org/show_bug.cgi?id=39724
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|directx-d3d |-unknown Summary|Need For Speed Underground |Need For Speed Underground |2: GL_INVALID_OPERATION in |2 crashes after several |glCopyTexImage2D(read |minutes of playing |buffer); (0x502) from | |glGenFramebuffers() | Alias|nfsu2_gl_invalid |
--- Comment #3 from Matteo Bruni matteo.mystral@gmail.com --- It's not obvious that those GL errors are related to the crash, after all the second log doesn't show them. Actually that log is from a different wine version and possibly a different prefix (GLSL shaders are reported as disabled only in that log).
Also log 1 was obtained while running the game on the Intel integrated GPU and log 3 on a dedicated Nvidia using primusrun or something like that, right? That's all stuff you should have mentioned when opening the bug.
https://bugs.winehq.org/show_bug.cgi?id=39724
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal
https://bugs.winehq.org/show_bug.cgi?id=39724
--- Comment #4 from Kolan Sh backbone@backbone.ws --- (In reply to Matteo Bruni from comment #3)
It's not obvious that those GL errors are related to the crash, after all the second log doesn't show them.
1st and 3rd logs only show GL errors, 2nd doesn't. I'm not familiar with this analysis.
Actually that log is from a different wine version and possibly a different prefix (GLSL shaders are reported as disabled only in that log).
I observe this behaviour for several last Wine versions 1.7.4x-1.7.55. I've made different Wine prefixes with different WINEARCH=win{32,64}, winetricks libraries but no luck.
Also log 1 was obtained while running the game on the Intel integrated GPU and log 3 on a dedicated Nvidia using primusrun or something like that, right?
Absolutely right!
That's all stuff you should have mentioned when opening the bug.
I haven't gather any more information.
https://bugs.winehq.org/show_bug.cgi?id=39724
--- Comment #5 from Kolan Sh backbone@backbone.ws --- Today I've installed the game on Debian Jessie x86_64 WINEARCH=win32 for different combinations of wine (1.6.2-20, 1.7.29), fglrx (14.9, 15.9) versions (from jessie-backports too) and clean ~/.wine prefix. The game crashes often when you are leaving the race.
Other games: GTA San Andreas, NFS Underground, NFS Most Wanted (requires d3dx9_36 only) work without any lags or problems on this configuration.
In this case I trust the Wine more than this game. May be it makes incorrect read*() actions or violate any memory protections...
https://bugs.winehq.org/show_bug.cgi?id=39724
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #6 from winetest@luukku.com --- Could you test 1.8.5 or 1.9.23 of wine? Or wine-staging 1.9 series?
https://bugs.winehq.org/show_bug.cgi?id=39724
--- Comment #7 from Kolan Sh backbone@backbone.ws --- (In reply to winetest from comment #6)
Could you test 1.8.5 or 1.9.23 of wine? Or wine-staging 1.9 series?
1.9.23 (binary): A few times the game crashed when loading data, but after a while this problem disappeared. I have played/tested few hours, switched to other windows many times, left home for a few hours and the game did not hang/crash for this time. Also I have played about 40 minutes next day without any problems.
1.9.22-staging (binary): After 5-10 minutes of playing when I have selected "Quick Race" and pressed 'Esc' Error Window was shown.
1.9.20-staging (system): Crashs Sometimes, but not often as it was when the ticked was created.
1.8.5 and 1.9.20 (binary): I have not seen the error message but I have not played for a long time, about 10-15 minutes only.
All the tests was performed under Gentoo, there is no other distributions nearby.
My conclusion is that clean Wine v1.9.23 (without any patches) is free of this bug (with concrete behaviour/exhibition) and the ticked should be closed and marked as fixed/resolved in the indefinite commit/version.
https://bugs.winehq.org/show_bug.cgi?id=39724
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dimesio@earthlink.net
--- Comment #8 from winetest@luukku.com --- You can mark bugs that you have created yourself as fixed. I didnt mean that you had to test all those versions, it's quite heavy task. Bugs should be opened and tested always against development version since the bug could be already fixed if using older version. And if its fixed already it will eventually land into next stable version.
https://bugs.winehq.org/show_bug.cgi?id=39724
Kolan Sh backbone@backbone.ws changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #9 from Kolan Sh backbone@backbone.ws --- So, I mark the bug RESOVLED->FIXED as it is not observed in the last release (1.9.23). Thank You!
https://bugs.winehq.org/show_bug.cgi?id=39724
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.9.24.
https://bugs.winehq.org/show_bug.cgi?id=39724
mirh mirh@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mirh@protonmail.ch
--- Comment #11 from mirh mirh@protonmail.ch --- I guess this was fixed either thanks to bug 40448, comment 5 or bug 40695, comment 7
-
wine-bugs＠winehq.org