diff options
| author | danakj@chromium.org <danakj@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-16 18:23:22 +0000 |
|---|---|---|
| committer | danakj@chromium.org <danakj@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-16 18:23:22 +0000 |
| commit | 2ab0352e52c75ccb3c0cc1d5c56d0cc09f19ff6c (patch) | |
| tree | 0a643aadd7b7c0ea5bb964ee122924f6ea3874b4 /cc/cc_tests.gyp | |
| parent | e9c7f0553447bb4127a5f3231b035ce8db6e7e08 (diff) | |
| download | chromium_src-2ab0352e52c75ccb3c0cc1d5c56d0cc09f19ff6c.zip chromium_src-2ab0352e52c75ccb3c0cc1d5c56d0cc09f19ff6c.tar.gz chromium_src-2ab0352e52c75ccb3c0cc1d5c56d0cc09f19ff6c.tar.bz2 | |
cc: Don't DeleteResource while holding write lock.
When the context is lost and we can't generate a mailbox for a
resource, we delete that resource. However currently we are already
optimistically holding a write lock on the resource.
Instead, only take the write lock once we have generated the mailbox
so we don't hold it when we delete the resource.
Tests:
VideoResourceUpdaterTest.SoftwareFrame
VideoResourceUpdaterTest.LostContextForSoftwareFrame
R=piman@chromium.org
BUG=260361
Review URL: https://codereview.chromium.org/19272005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@211815 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'cc/cc_tests.gyp')
| -rw-r--r-- | cc/cc_tests.gyp | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/cc/cc_tests.gyp b/cc/cc_tests.gyp index d4c4586..ff5b40b 100644 --- a/cc/cc_tests.gyp +++ b/cc/cc_tests.gyp @@ -60,6 +60,7 @@ 'resources/scoped_resource_unittest.cc', 'resources/tile_manager_unittest.cc', 'resources/tile_priority_unittest.cc', + 'resources/video_resource_updater_unittest.cc', 'resources/worker_pool_unittest.cc', 'scheduler/delay_based_time_source_unittest.cc', 'scheduler/frame_rate_controller_unittest.cc', |