We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 3450 - Screen flickers on radeon 470RX 4 gig
Summary: Screen flickers on radeon 470RX 4 gig
Status: RESOLVED ABANDONED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 2.0.4
Hardware: x86_64 Windows 10
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-12 17:17 UTC by Michael Staud
Modified: 2018-08-06 21:20 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Staud 2016-10-12 17:17:39 UTC
Hey, I am developing a game with SDL2 and OpenGL. I got from one of my players the notice that the game is unplayable because of screen flickering on his radeon 470RX 4 gig. He recently updated the graphics card and it was the first time he tried the game with the new graphics card. The exact hardware is the following:

windows 10,lenova A10 AMD 64 3.5 quad(8thread 12 core) 16 gigs of memory, 
Radeon RX470 4 Gig video card. 
with the Radeon 16.7.3 driver version. he also tried the 16.9.2 driver.

I cannot reproduce the bug on our computers. I tested it on amd, nvidia and intel graphics cards and my game worked fine. So I assume that it has nothing do to with my code (or?). 

If you think that it could be my code how would you find such a bug?
Comment 1 Alex Szpakowski 2016-10-12 19:46:22 UTC
There are a lot of ways to cause undefined or otherwise undesirable behaviour when writing OpenGL code. I recommend using the OpenGL debug callback mechanisms[1] as well as running your game through an OpenGL debugger such as RenderDoc, AMD CodeXL, nvidia nsight, etc.

[1]: https://www.opengl.org/wiki/Debug_Output
Comment 2 Michael Staud 2016-10-13 17:23:37 UTC
Thanks for your answer. I only knew about the "old" OpenGL error report functions and with these everything was fine. I will check the new ones out.

The player now tested the newest version of the game and described the error more clearly:

"I didnt have screen flicker it starts in 800 x 600 and fills up only 60% of my screen. When i click anything. It flashes like its trying to adjust resolution with my 40" inch screen. Then its really offset and i have no mouse control to try again. I have to click windows to exit game. I noticed it was a little different this time but same results. It seemd to actually fill my screen a little better but did not fix problem."

Starting in 800x600 in window mode is ok. The game is programmed to do this when it is first installed.

Then he got the following error messages:

OpenGL Renderer: Radeon (TM) RX 470 Graphics
OpenGL Version: 4.5.14009 Compatibility Profile Context 21.19.151.3
OpenGL Shader: 4.50
[0x7FF824B67CC0] ANOMALY: meaningless REX prefix used
[0x7FF82CDB4250] ANOMALY: meaningless REX prefix used
[0x7FF82436CDB0] ANOMALY: meaningless REX prefix used
[0x7FF824B6DF20] ANOMALY: meaningless REX prefix used
[0x7FF824B6DF80] ANOMALY: meaningless REX prefix used
[0x7FF824B6DFE0] ANOMALY: meaningless REX prefix used
[0x7FF824378E10] ANOMALY: meaningless REX prefix used
[0x7FF824378FD0] ANOMALY: meaningless REX prefix used
[0x7FF824379120] ANOMALY: meaningless REX prefix used
[0x7FF8243794E0] ANOMALY: meaningless REX prefix used
[0x7FF824379520] ANOMALY: meaningless REX prefix used
[0x7FF824379430] ANOMALY: meaningless REX prefix used

That means that the machine code is corrupted. Never had this kind of error on any of my computers. Used the normal mingw compiler without assembler to create the executables (and I suppose you guys do the same). It only appeared after he upgraded the graphics card.
Comment 3 Ryan C. Gordon 2018-08-06 21:20:20 UTC
Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.