Comment #4 on issue 4808 by [email protected]: Content area stops updating sometimes http://code.google.com/p/chromium/issues/detail?id=4808
The problem is that when we process a windows event, we sometimes: a) pop off the reminder event b) pop a windows event to get ready to process it. c) turn off the boolean to indicate there is no reminder pending d) process the event from (b) above e) when we get back (oops) do work from our queue and post another reminder event. The current (plausible) fix is to put a potentially wasteful (unnecessary?) reminder event in place just before step (d)'s processing (and only if we have stuff to do in d) above. We might come right back from (d), do (e), and not have any more stuff to do (and hence not need another reminder). Hence it is possibly wasteful. On teh other hand, when we have big backlogs, and lots of work to do, then it is not really much of a waste (there will be a bunch of windows events pending, and a rare addition of a reminder event should not make a difference). Note that we probably can't (for example) pop the event, and then do private work, and then do the popped event. The problem is that when we do work, we MIGHT do a pile of windows events processing, and allow other queued events to bypass the one we popped in (b). This is why the issue is a problem :-/. (it even had a todo() in the code around this point). -- 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
