This behavior is by design. The usual approach is to use UpdateProgress
control that disables the user input on the page while the postback is in process.
Alternatively you could add your own onchange
event handlers that call __doPostBack()
more intelligently (by using timers etc.) to avoid this problem for your specific scenario. You could also try aborting any postback is process before submitting a new one.
A resource that might be useful: http://www.dotnetcurry.com/ShowArticle.aspx?ID=176