Random graphics glitch

[Glocke]

Hi, I'm facing a random graphics glitch. The glitch is shown in the following video:

It occures at some random position... sometimes while drawing render textures to the screen, sometimes without doing so. Toggling between drawing those or not always fixes the glitch (temporarily).
Unfortunately I cannot reproduce this behavior, because the positions seem to be "random". Sometimes the behavior does not occur. Sorry, but I cannot test the entire problem on a different machine. I also cannot reduce the problem to a minimal code example - the problem occures too randomly

I'm using SFML 2.2 (Release source + small joystick fix). But I was facing this problem also with a prior version (maybe 2.1) some months ago (within another project using SFML)
The machine is a netbook (running Ubuntu) with an Intel GPU. I know that those GPUs (especially with linux graphics drivers) often cause problems. I also upgraded my graphics card driver to the latest version using a tool by Intel.

I'd like to know whether other people also faced similar behaviors at their projects.

Kind regards

[eXpl0it3r]

You know if you used the actual YouTube link without HTTPS it would automatically get embedded.

For me it seems like some vertices get wrongly positioned.



Are you should it's not a mistake in your code?
Otherwise I haven't heard of such an issue...

[Glocke]

You know if you used the actual YouTube link without HTTPS it would automatically get embedded.

Ahh thanks

For me it seems like some vertices get wrongly positioned.
Are you should it's not a mistake in your code?
Otherwise I haven't heard of such an issue...

Well, I'll check for wrongly positioned vertices! I guess that might be the reason

[Glocke]

I realized, that the behavior has something to do with rendering the hud (life/mana/stamina bars and the green line, which represents a calculated path - debugging purpose).
I just faced a situation where the entire screen is blackened and those yellow/green stuff is drawn. The entire scene and the entire hud are deleted (the other onscreen logging such as the "SYSTEM RUNTIME" etc. aren't part of the hud).
When toggling those draw-the-path-for-debugging-purpose (I implemented this via shortcut), the entire glitch disappears. Also, when drawing another "debugging thing" (e.g. showing the grid or the collision map), the glitch also disappears. When toggling the system monitor, the entire yellow-red-stuff and the system monitor are flickering.
Well, to be honest, I think thats my graphics driver's fault. When turning parts on/off (e.g. to show grid borders, collision information or lighting) the glitch is shown/hidden

I also had these three parts (grid borders, collision info, path-"lines") in my old project but rewrote them competly. Any suggestions how I can debug this situation? I'm familar with debugging in general (using gdb) but I don't know where to start here :S

/EDIT: After toggling those settings on and on, the game crashed (Segmentation Fault). So I ran it inside the debugger, seeked another glitch-spot (hard to find but I found one) and repeated it. Then, some reeeally weird stuff happened: not just flickering glitches but also "rolling" horizontal lines (moving randomly up and down). After randomly toggling the settings, it crashed again and the debugger said:

intel_do_flush_locked failed: Invalid argument
[Inferior 1 (process 14407) exited with code 01]
(gdb) bt
No stack.
 

XD

/EDIT: Now, this message occures also for other programs. E.g. when running totem (video player) it crashes with intel_do_flush_locked failed: Das Argument ist ungültig (which is the equivalent message in German). I'm gonna restart

[Dejan Geci]

If it happens in other software, it just might be a hardware/driver issue. Try to update the driver, and also try your application on another computer to verify it's working correctly.

[Nexus]

Are you using raw OpenGL or another library that has its own rendering (e.g. GUI)? Or only SFML?

You could also try to use another driver if there's one available. Not a different version, but a different developer. For example, proprietary drivers from the vendor (Intel) or Mesa ones.

[Glocke]

Are you using raw OpenGL or another library that has its own rendering (e.g. GUI)? Or only SFML?

I'm using pure SFML. Also my GUI rendering is based on SFML (Drawables etc.)

You could also try to use another driver if there's one available. Not a different version, but a different developer. For example, proprietary drivers from the vendor (Intel) or Mesa ones.

Ok I'll check this if I'm in the mood for driver adventures

[Nexus]

Be careful on Linux. By installing the wrong driver, I already managed to mess up literally everything

Maybe you should first try to isolate the problem... That would also be helpful to workaround the issue, or even more if it's not actually a driver problem.

[Glocke]

Be careful on Linux. By installing the wrong driver, I already managed to mess up literally everything

Me too. That's why I wrote "driver adventures"

Maybe you should first try to isolate the problem... That would also be helpful to workaround the issue, or even more if it's not actually a driver problem.

Unfortunatley I have no idea where to start. Traditional debugging approaches don't seem to help me here

[dabbertorres]

There are no proprietary Intel graphics drivers for Linux, just fyi. Intel published their graphics driver code as open source.

Mesa IS the Intel 3D graphics driver on Linux.

What is your kernel version (run: "uname -v")? Some googling for "intel_do_flush_locked failed: Invalid argument" found this kernel bug report. Looks like a patch made it into kernel 3.18.4 from here.