GitLab

CHECK is very aggressive - saving bad data is generally not a show
stopper (except for data that causes FLT_EXCEPTIONS on win). The idea
is to let this sit in pre-beta channels for a bit and find out if there
are any remaining ways we can cause corrutpion.

TODO(me): revert this before beta promotion.

Bug: 982009
Change-Id: If2faf12e56a54bd7244f08aa940be2ace9781ca4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1855199
Auto-Submit: Chrome Cunningham <chcunningham@chromium.org>
Commit-Queue: Frank Liberato <liberato@chromium.org>
Reviewed-by: Frank Liberato <liberato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#704998}