GSKeyEvent race condition.

[GoogleCodeExporter]

This bug could be seen only in threaded mode.

O'k, I was tracking down some ZeroGS segfault and found strange thing:
GSKeyEvent does not put to GS thread, but it worked in VSync thread. So in
ZeroGS pressing F6 cause BOTH threads using the graphic's and even more,
one of the threads want FBO destruction witch used by another.

In Windows version this race overlaped by manualy hanfled GSKey's in
GSThread's GSVsync. It's not good, but could be accepted.

So there is 2 ways of resolving this race:
1) redone GSThread to add singal to GSKeyEvent 
2) do not touch anything rather plugin, and state that pluggin author must
be avare that GSKeyEvent function is not in proper thread,

Original issue reported on code.google.com by Zeydl...@gmail.com on 16 Nov 2008 at 11:56

[GoogleCodeExporter]

I'm finally putting this on my soon-todo list.  Should have it fixed soon. :)

Original comment by Jake.Stine on 25 Dec 2008 at 12:32

• Changed state: Started
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Well, I fixed it yet by redone ZeroGS code a little.

Original comment by Zeydl...@gmail.com on 25 Dec 2008 at 4:27

[GoogleCodeExporter]

Original comment by arcum42@gmail.com on 29 Apr 2009 at 9:07

• Changed state: Fixed