cc: Fix logic for detecting when raster tasks were throttled

The PixelBufferRasterWorkerPool checks whether raster tasks were
throttled to avoid notifying the client that all pending tasks were
completed too early. The current logic for this fails if tasks from the
previous graph were still active when we schedule a new graph. In these
situations we end up thinking some tasks were throttled and will not
schedule the final sentinel task to indicate work completion. This can
lead to delayed tree activation.

The fix is to only consider tasks from the new work queue when seeing if
any got throttled.

BUG=331534

Review URL: https://codereview.chromium.org/131763003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243962 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 243962
Removal of GetDefaultProfile for new charger messages

As discussed - it's time to get rid of the GetDefaultProfile now.

BUG=322682
TEST=covered by existing unit tests

Review URL: https://codereview.chromium.org/128583002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243963 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 243963