summaryrefslogtreecommitdiffstats
path: root/build/install-build-deps.sh
diff options
context:
space:
mode:
authorsiva.gunturi <siva.gunturi@samsung.com>2015-01-06 03:11:20 -0800
committerCommit bot <commit-bot@chromium.org>2015-01-06 11:12:15 +0000
commit67d1a03057042dfc9bb0a71f9906320ee5204301 (patch)
tree0c99e5ea0bd30523e99c8262e9cd0d603555b58f /build/install-build-deps.sh
parentf3a423692d7157d1f650149bea4674e5d5b230d0 (diff)
downloadchromium_src-67d1a03057042dfc9bb0a71f9906320ee5204301.zip
chromium_src-67d1a03057042dfc9bb0a71f9906320ee5204301.tar.gz
chromium_src-67d1a03057042dfc9bb0a71f9906320ee5204301.tar.bz2
Revert of Validate Bucket data in ShaderSourceBucket. (patchset #6 id:100001 of https://codereview.chromium.org/822953002/)
Reason for revert: No need to check for memory allocation failure. New never returns NULL. In Chrome we explicitly abort (crash) before returning from the allocator in case of allocation failure. Original issue's description: > Validate Bucket data in ShaderSourceBucket. > > As of now only the received bucket and > the size of bucket are validated. We > should check for validation of bucket > data before we start using it and report > failures. > > BUG= 240467 > > Committed: https://crrev.com/6df438ed2adaf24fa2f4a92d4f3863825247b910 > Cr-Commit-Position: refs/heads/master@{#309882} TBR=sievers@chromium.org,piman@chromium.org,bajones@chromium.org,zmo@chromium.org NOTREECHECKS=true NOTRY=true BUG= 240467 Review URL: https://codereview.chromium.org/802323005 Cr-Commit-Position: refs/heads/master@{#310078}
Diffstat (limited to 'build/install-build-deps.sh')
0 files changed, 0 insertions, 0 deletions