Status: Unconfirmed Owner: ---- Labels: Type-Bug Pri-2 OS-All Area-Misc New issue 9656 by omattos: Incorrect ordering of Mouse click and move events. http://code.google.com/p/chromium/issues/detail?id=9656
Chrome Version : 2.0.171.0 URLs (if applicable) : any Other browsers tested: Does not apply to other browsers/applications What steps will reproduce the problem? 1. Ensure the system is under memory or cpu pressure. (eg. open a 700 meg file in notepad or keep hitting "cubed" in windows calculator) 2. open two or more tabs in chrome. make sure tab A is selected. 3. click tab B, and then immediately after clicking move the mouse downwards. What is the expected result? The mouse should move downwards. The contents of tab B should be shown in the main window. What happens instead? The mouse moves downwards, but dragging tab B with it as if the mouse button were still pressed. A few seconds later chrome processes the "mouse up" event, and the tab is released into a new window. Please provide any additional information below. Attach a screenshot if possible. There are two possible causes here: 1. Mouse events are not processed in the order they are received - if mouse move events are processed before mouse up/down events, we would see this behaviour. 2. The application somehow uses the mouse "current position" when handling the mouse click event - this is wrong, since it should use the position of the mouse when the click event occured rather than the current position, since they may not be the same if the application is processing messages slowly. Reproduction notes: This happens very frequently on low memory machines when switching tabs as the buffer containing the rendered bitmap of a background tab has been paged to disk, and the application is stalled while paging it back. To reproduce, I suggest finding a vista machine with the minimum spec for vista (512M) and running a few apps at the same time as chrome. It is also possible to reproduce with pressure on the CPU only by using windows calculator with above normal priority, but it occurs much less often this way. Even though this is hard to reproduce, it could be a common problem in the field with users running hundreds of background tasks (some power users may keep > 200 tabs open at any given time in various browsers, which means keeping bitmaps of all those tabs in ram becomes less likley) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
