http://bugs.winehq.org/show_bug.cgi?id=59986 --- Comment #11 from TOM <l12436.tw@gmail.com> --- Created attachment 81468 --> http://bugs.winehq.org/attachment.cgi?id=81468 Log by +event,+event,+xinput,+win,+msg I am using kde 5.27 This is how I found the weird part, if you grep '67 raw frames' you will see the following log 0024:trace:win:send_mouse_motion Sending pos (6,0), flags 0, data 0x6, time 0 (67 raw frames) 0024:trace:win:accum_mouse_motion Keeping pos (0,-2), flags 0xffffffff, data 0, time 0 (67 raw frames) 0024:trace:win:send_mouse_motion Sending pos (0,-2), flags 0xffffffff, data 0, time 0 (67 raw frames) but according to the code TRACE( "Keeping %s (%u raw frames)\n", debugstr_mouseinput( &info->mouse_motion.mi ), info->raw_mouse.count ); info->raw_mouse.count show 67. but the raw_mouse define only contain 64 data struct raw_mouse { UINT count; POINT data[64]; /* arbitrary buffer size */ }; so I think the count should never shown 67 no matter what. that is buffer overflow Also if you search '65 raw frame' you will also see this 0024:trace:win:accum_mouse_motion Keeping pos (0,0), flags 0, data 0, time 0 (65 raw frames) 0024:trace:win:accum_mouse_motion Keeping pos (0,0), flags 0, data 0, time 0 (65 raw frames) the data complete zero. but count still increase So i think code in send_mouse_motion return too earily I think. maybe there are raw frame there. but code did not send it. due to the following condition if (!input.mi.dwFlags && !input.mi.mouseData) return STATUS_SUCCESS; /* ignore empty inputs */ -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.