This means that trying to read a blob containing filesystem URL elements through these methods will result in a crash.
Fixing is somewhat non-trivial, as it means BlobImpl needs to somehow get access to a FileSystemContext, and thus all sites that create a BlobImpl might also need fixing.
Other options could include:
- store the FileSystemContext in the BlobDataHandle
- or store the FileSystemContext in the individual BlobDataItems when those items actually represent filesystem URLs
I actually kind of like that last option, as it gets us somewhat closer to items abstracting away how they are read (making BlobReader need to know less about individual item types), and possibly eventually moving to filesystem entry items, disk cache entry items etc all just being some mojo interface to another part of the system (hopefully ultimately removing all knowledge of disk cache and filesystem APIs from the blob system).
Comment 1 by bugdroid1@chromium.org
, Nov 27 2017