Revert of Check for 0-length files in ResourceExtractor (patchset #3 id:40001 of https://codereview.chromium.org/1920893003/ )

Reason for revert:
Possibly regressed memory usage on android (http://crbug.com/607598)

Speculative revert to see if vm_private_dirty_final_browser values go back down for android bots on the perf waterfall

Original issue's description:
> Check for 0-length files in ResourceExtractor
>
> Also moves from an on-disk version timestamp file to SharedPreferences
> (should be faster).
>
> BUG=606413
>
> Committed: https://crrev.com/b28607d4c72261657ea9e24ea9195bc23a472b3f
> Cr-Commit-Position: refs/heads/master@{#390068}

TBR=yfriedman@chromium.org,torne@chromium.org,wnwen@chromium.org,agrieve@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=606413

Review-Url: https://codereview.chromium.org/1948033004
Cr-Commit-Position: refs/heads/master@{#393023}


CrOS-Libchrome-Original-Commit: a3f2dd5d896ca693224403ad072cfad70882174b
1 file changed
tree: e20042257d825d8db42e3775f9ba6ac7188d81b1
  1. base/
  2. build/
  3. components/
  4. dbus/
  5. device/
  6. ipc/
  7. mojo/
  8. testing/
  9. third_party/
  10. ui/