Invalid NS_ERROR_FILE_CORRUPTED error during large transaction (w/testcase)




11 years ago
10 years ago


(Reporter: dan-bugzilla, Unassigned)


1.8 Branch

Firefox Tracking Flags

(Not tracked)



(1 attachment)

1.74 KB, application/x-xpinstall


11 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv: Gecko/20070725 Firefox/
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv: Gecko/20070725 Firefox/

Database corruption error testcase at shaver's and mfinkle's request in #extdev.

The database passes PRAGMA integrity_check. This particular testcase does not actually corrupt the database, but we've seen that happening as well--will try to come up with a simple testcase for that.

A dump and restore of the database, a VACUUM, or the deletion of tables causes the test to pass.

Reproducible: Always

Steps to Reproduce:
1. Install corruptdb.xpi (attached)
2. Download and extract db.sqlite to %PROFILE_DIR%/extensions/
3. Load chrome://corruptdb/content/corrupt.xul
Actual Results:  
executeSimpleSQL fails with an NS_ERROR_FILE_CORRUPTED error, and a "fail" message appears.

Expected Results:  
SQL transaction should complete successfully, and a "pass" message should appear.

Reproduced on OS X and Windows XP. Does not happen in 3.0a7 (though rather problematic for our users in

Sorry for the DB size. This is a database from a user, with unnecessary tables removed and most remaining data replaced with gibberish strings.

Comment 1

11 years ago
Created attachment 277977 [details]
Test Case Extension


11 years ago
Version: unspecified → 1.8 Branch
hrm, we have an older version of sqlite on branch...

Comment 3

11 years ago
For what it's worth, I just tried the command-line client for SQLite 3.3.4 (which, as far as I can tell, is the version in and the same transaction works fine.
I'm sorry to say that we won't be fixing this on branch (for Firefox 2.0).  The good news is that Firefox 3.0 is using a much newer version of SQLite (version 3.5.9), so you shouldn't see this in Firefox 3.  Sorry this doesn't work for Firefox 2.0.
Last Resolved: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.