User Agent: Mozilla/5.0 (Windows NT 5.1; rv:18.0) Gecko/20100101 Firefox/18.0 Build ID: 20130104151925 Steps to reproduce: 1. Create a XULRunner application that opens an IndexedDB database 2. Configure the application to use a profile on a network drive (e.g. \\server\profile) 3. Attempt to open and use the database Actual results: The IDBOpenRequest fails with error UnknownError Expected results: The database should have opened
This scenario succeeds in Mozilla 19.0.2 (and all previous versions with IDB support). I've tried with the latest nightly build (23.0a1) and got the same UnknownError. This error occurs on both Windows XP and Windows 7.
I forgot to mention that when the same network drive is mapped to a drive letter (e.g. X:\profile), and the application is configured to use the mapped drive for it's profile location, the scenario laid out above succeeds as expected.
(In reply to poppertd from comment #1) > This scenario succeeds in Mozilla 19.0.2 (and all previous versions with IDB > support). I've tried with the latest nightly build (23.0a1) and got the > same UnknownError. This error occurs on both Windows XP and Windows 7. So there is a possible regression since Firefox 20. Could you use the tool mozregression (see http://harthur.github.io/mozregression/ for details) and find a regression range. First Firefox 20 nightlies started in Nov 2012 (mozregression --good=2012-11-01). You should create a new networked profile to use mozregression, it's advised.
I'll work on using mozregression shortly. In the meantime, I have some info from a debug enabled build I created this morning. The specific line that fails is http://mxr.mozilla.org/mozilla-release/source/storage/src/mozStorageConnection.cpp#533 (::sqlite3_open_v2(spec.get(), &mDBConn, mFlags, NULL)) with an error of NS_ERROR_FILE_ACCESS_DENIED (0x80520015). Working my way up the stack, Mozilla 20 opens the connection to SQLite using mozIStorageService#openDatabaseWithFileURL, while Mozilla 19 uses mozIStorageServiceQuotaManagement::openDatabaseWithVFS.
Any luck yet to get a Regression Range?
Please see bug 879133 for the regression