Bug 31462 - Chromium should not register its VFS as the default VFS
Summary: Chromium should not register its VFS as the default VFS
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Dumitru Daniliuc
Depends on:
Reported: 2009-11-13 00:46 PST by Dumitru Daniliuc
Modified: 2009-11-13 11:34 PST (History)
2 users (show)

See Also:

patch (2.87 KB, patch)
2009-11-13 01:04 PST, Dumitru Daniliuc
dglazkov: review+
dumi: commit-queue-
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Dumitru Daniliuc 2009-11-13 00:46:57 PST
Currently Chromium registers its HTML5 DB-specific VFS as the default VFS in all renderer processes. This is fine as long as HTML5 DBs is the only feature using sqlite databases in those processes. However, as soon as there are other sqlite DB users in the same process (DB tracker in test_shell, for example), they fail, because they don't expect to deal with a custom VFS. To fix this, we should keep the default sqlite VFS as the default VFS, and the HTML5 DB code can explicitly call the custom VFS by name.
Comment 1 Dumitru Daniliuc 2009-11-13 01:04:21 PST
Created attachment 43147 [details]
Comment 2 Dimitri Glazkov (Google) 2009-11-13 07:26:39 PST
Comment on attachment 43147 [details]

Comment 3 Dumitru Daniliuc 2009-11-13 11:34:10 PST
Landed as r50954.