You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported in version: HG 2.0 Reported for operating system, platform: Linux, All
Comments on the original bug report:
On 2013-04-18 05:36:33 +0000, driedfruit wrote:
Created attachment 1116
gdb backtrace
On X11, sometimes, when you move your mouse and release the keyboard
key at the same time, you get a SIGSERV crash.
I've "tracked" it down to the X11_KeyRepeat function in
SDL_x11events.c. The function looks for next X11 event in the queue and
compares it to the current one, working around keyboard auto-repeat
feature of X11.
The culprit is XPeekEvent, which either crashes itself, either
corrupts something, so next XNextEvent call crashes.
To easier reproduce this, change "2" to "10" or a larger value here:
Applying this patch to 1.4.1 libXi fixes the issue. It's part of the more recent libXi releases. Sorry!
On 2013-07-15 15:31:48 +0000, Steve Soule wrote:
Created attachment 1236
patch to workaround this libXi bug
This patch is a workaround for the bug in libXi. It avoids calling X functions that trigger the bug. See the forum thread http://forums.libsdl.org/viewtopic.php?p=38071 for my explanation of what this workaround is intended to do.
On 2013-07-16 03:30:51 +0000, Sam Lantinga wrote:
Reopened to investigate Steve's patch.
On 2013-07-18 23:05:10 +0000, Ryan C. Gordon wrote:
That email thread has some really impressive research.
This patch looks good to me. Sam, you want to give this a looking at before I apply it?
Thanks,
--ryan.
On 2013-07-20 01:40:12 +0000, Sam Lantinga wrote:
It looks good to me. Go for it. Great work everyone!
On 2013-07-20 13:12:26 +0000, Ryan C. Gordon wrote:
This bug report was migrated from our old Bugzilla tracker.
These attachments are available in the static archive:
Reported in version: HG 2.0
Reported for operating system, platform: Linux, All
Comments on the original bug report:
On 2013-04-18 05:36:33 +0000, driedfruit wrote:
On 2013-04-18 05:37:03 +0000, driedfruit wrote:
On 2013-04-18 05:37:39 +0000, driedfruit wrote:
On 2013-04-18 19:08:30 +0000, Ondra Hošek wrote:
On 2013-04-19 02:38:42 +0000, driedfruit wrote:
On 2013-04-30 11:10:05 +0000, driedfruit wrote:
On 2013-07-15 15:31:48 +0000, Steve Soule wrote:
On 2013-07-16 03:30:51 +0000, Sam Lantinga wrote:
On 2013-07-18 23:05:10 +0000, Ryan C. Gordon wrote:
On 2013-07-20 01:40:12 +0000, Sam Lantinga wrote:
On 2013-07-20 13:12:26 +0000, Ryan C. Gordon wrote:
On 2013-07-27 00:33:18 +0000, Ryan C. Gordon wrote:
The text was updated successfully, but these errors were encountered: