{"push_id":1226924993,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"fae0fb34ab73f12a8be3493f0ec06dbbb32c7b20","before":"faa993577f164eb212d5b363e90180a85139ea74","commits":[{"sha":"fae0fb34ab73f12a8be3493f0ec06dbbb32c7b20","author":{"name":"enne","email":"cf5dfe2bae3f84f8399fbaf49f47af1c27dfed87@chromium.org"},"message":"Fix bug with blank pages during navigation\n\nThis bug started after r408172.  In some situations when navigating, the\nSetNeedsBeginFrame messages that is sent from the\nCompositorExternalBeginFrameSource to the RenderWidgetHostView, but is\nreceived by the RenderWidgetHostImpl while the RenderViewHost is swapped\nout and before it has swapped back in.  In these cases, if this message\nis dropped, the renderer will never tick new frames and the tab will\nfreeze.  This appears to be racy, as the renderer finds out that it is\nvisible and sends this message before the view host is swapped in.\n\nTo fix this race, always allow the SetNeedsBeginFrame message to be\nreceived while being swapped out so that the RenderWidgetHostView can be\nin the correct state when it is swapped in.\n\nR=sievers@chromium.org\nBUG=632276\n\nReview-Url: https://codereview.chromium.org/2197783002\nCr-Commit-Position: refs/heads/master@{#408787}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/fae0fb34ab73f12a8be3493f0ec06dbbb32c7b20"}]}
{"actor":{"display_login":"dstockwell"}}