The program seems to do exactly this. Or which amount of events do you expect from moving your mouse for two seconds?
The output stream from my previous post shows the number of events processed on each frame. If the mouse moved during that frame, I would expect to see a '1' printed out not 13 or 222.
As long as I keep moving my mouse, events continue to be accumulating in the event queue and the program STOPS COMPLETELY until the mouse stops generating new events (ie. I take my hand off it).
The behavior I would expect is that as I move the mouse, on each frame a new single event is created and the program moves onward. As it is now, I can effectively pause my program indefinitely by continually moving my mouse around the screen. Oddly enough, I have the same problem with SDL on my machine only the events stop queue up at a certain limit and the program moves on resulting in intermittent stop/go/stop behavior while the mouse is moving.
I will reproduce the bug with minimal code and post it this weekend. Thanks!