indexeddb: check for missing filesystem_proxy in backing store
https://chromium-review.googlesource.com/c/chromium/src/+/2365358 added the use of filesystem_proxy, but for in memory databases it is null. Previously this was handled because blob_path was set to empty, and so removing empty files would fail silently in the base file_util functions. Now, with a null filesystem proxy, it would crash. Instead of implicitly failing, explicitly check for the filesystem_proxy where needed. Bug: 1122011 Change-Id: I5e79e89c380e0e2ad9a4f80f14bcd614564b8940 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2382392Reviewed-by:Daniel Murphy <dmurph@chromium.org> Commit-Queue: enne <enne@chromium.org> Cr-Commit-Position: refs/heads/master@{#802780}
Showing
Please register or sign in to comment