summaryrefslogtreecommitdiffstats
path: root/chrome/renderer/DEPS
diff options
context:
space:
mode:
authorcmasone@chromium.org <cmasone@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-11-02 16:29:30 +0000
committercmasone@chromium.org <cmasone@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-11-02 16:29:30 +0000
commit0c23428a4ffe32a614580b330b66e5b4448fc7af (patch)
treea2c4479b4d2a674efbca238e5961d0c67e82dac2 /chrome/renderer/DEPS
parentb84129962c1fb9f411ed6acf9f263fbf1f40e959 (diff)
downloadchromium_src-0c23428a4ffe32a614580b330b66e5b4448fc7af.zip
chromium_src-0c23428a4ffe32a614580b330b66e5b4448fc7af.tar.gz
chromium_src-0c23428a4ffe32a614580b330b66e5b4448fc7af.tar.bz2
[cros] migrate to safe ownership API
I was passing memory from libcros to chrome and expecting chrome to free it. I was also passing vectors across the DLL boundary. These could both cause memory horkage. Having implemented safe alternatives in http://codereview.chromium.org/4132006, migrate to them. Depends on cros_deps roll in http://codereview.chromium.org/4207004/show BUG=chromium-os:8283 TEST=install on the device, log in as the first account, whitelist users, disable BWSI Review URL: http://codereview.chromium.org/4240001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@64756 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/renderer/DEPS')
0 files changed, 0 insertions, 0 deletions