Comment #10 on issue 16059 by ajw...@chromium.org: Stop() should be asynchronous and should receive a callback http://code.google.com/p/chromium/issues/detail?id=16059
An unfortunate side effect of this is that VideoRenderBase::OnReadComplete may have been scheduled while Stop() is called. Thus, the state_ may be moved into kStopped with and outstanding OnReadComplete posted into the message loop. In this situaiton, OnReadComplete may execute when the pipeline thinks the filter has stopped. Bad bad. There's a workaround in r23514, but making Stop fully asynchronous is the "right" solution. -- 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 -~----------~----~----~----~------~----~------~--~---