Closed Bug 583867 Opened 15 years ago Closed 13 years ago

Places AutoComplete: [xpconnect wrapped mozIStorageError] when using the awesomebar

Categories

(Firefox :: General, defect)

4.0 Branch
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: msclrhd, Unassigned)

References

Details

(Keywords: regression)

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b3pre) Gecko/20100802 Minefield/4.0b3pre Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b3pre) Gecko/20100802 Minefield/4.0b3pre Using the awesome bar (e.g. to search for gmail) I get the following error: Error: Places AutoComplete: [xpconnect wrapped mozIStorageError] Source File: file:///home/reece/Downloads/firefox-4.0b3-x86_64/components/nsPlacesAutoComplete.js Line: 500 Reproducible: Always
blocking2.0: --- → ?
Keywords: regression
Also seeing on Mac OS X, with a Tab Candy build though: Error: Places AutoComplete: [xpconnect wrapped mozIStorageError] Source File: file:///Applications/TabCandy.app/Contents/MacOS/components/nsPlacesAutoComplete.js Line: 500
OS: Linux → All
Hardware: x86_64 → All
Does the search work as expected? What's the actual bug here outside of this error in the console?
The search *appears* to work -- it is returning results that look correct. The output may be related to bug 583810 (Error 400: Bad Request when loading GMail -- (NS_ERROR_FILE_CORRUPTED) [nsIBrowserHistory.registerOpenPage]). I will retest these with the next build when it is available. In the error output, the mozIStorageError is not decoded, but speculating since this happens in conjunction with bug 583810 (this on the awesomebar, bug 583810 when navigating to the page), I suspect this is a NS_ERROR_FILE_CORRUPTED.
Seeing the error in nightly build [Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b3pre) Gecko/20100803 Minefield/4.0b3pre] Error: Places AutoComplete: [xpconnect wrapped mozIStorageError] Source File: file:///Applications/Minefield.app/Contents/MacOS/components/nsPlacesAutoComplete.js Line: 500
Depends on: 584111
I filed bug 584111 to get some better error logging on nightlies here.
the library (Show All History) is completely broken as well, sounds related: Error: this.view is null Source File: chrome://global/content/bindings/tree.xml Line: 712 when I open the library.
I'm getting a different error when using the 'Show All History' dialog: Error: Async statement execution returned with '11', 'database disk image is malformed' Source File: file:///home/reece/Downloads/firefox-4.0b3-x86_64/components/nsPlacesExpiration.js Line: 670 Also, I am getting: Error: uncaught exception: [Exception... "Component returned failure code: 0x8052000b (NS_ERROR_FILE_CORRUPTED) [nsIBrowserHistory.registerOpenPage]" nsresult: "0x8052000b (NS_ERROR_FILE_CORRUPTED)" location: "JS frame :: chrome://browser/content/tabbrowser.xml :: anonymous :: line 504" data: no] ... but no longer when accessing Gmail -- I have seen it on startup and when following through GoogleReader links. I don't have any direct correlation. Also, this is with Cookies and Cache cleared. :(
Sounds to me like your places database is corrupted.
The [nsIBrowserHistory.registerOpenPage] is happening consistently on URL navigation (clicking on an anchor tag), but does not trigger when entering a page in the awesomebar.
The corruption probably happened when I started getting the 'Bad Request' errors. I'll run a clean profile and see if that sparks another corruption. Do you know anything about the SQL DB rewrite? -- When I read up on that defect, I recall that the patches were lax on corruption checks. Did any of those changes land for the 2nd Aug build?
(In reply to comment #10) > Do you know anything about the SQL DB rewrite? I don't know anything about any SQL DB rewrite, and I'm the person most likely to know. What do you mean?
(In reply to comment #6) > the library (Show All History) is completely broken as well, sounds related: > > Error: this.view is null > Source File: chrome://global/content/bindings/tree.xml > Line: 712 > > when I open the library. bug 582661
Shawn: I was thinking of bug 572223 with the "Ignore corruption for now." comments.
That would have nothing to do with places, and "ignoring" corruption was already happening with cookies.
Ok, thanks for the clarification. Not sure what happened here. I am now running on a fresh profile on this machine (running ok so far). I am going to experiment with: fresh profile (older Minefield) -> 2nd Aug build -> 3rd Aug build fresh profile (older Minefield) -> 3rd Aug build to see if I can recreate the places corruption, as other people have reported the mozIStorageError issue.
Renominate once we get clear steps to reproduce, please.
blocking2.0: ? → ---
I'm willing to be this was fallout from SQLite 3.7.0, which was backed out.
Version: unspecified → 4.0 Branch
This bug was reported using a pre-release version of Firefox 4. Now that Firefox 4.0.1 final has been released, can you please update and retest your bug? A fresh profile would be a good starting place to test, http://support.mozilla.com/kb/Managing+profiles. If you continue to see the issue, can you please update this bug with your results? Filter: firefox4prebugsunco
time to close this?
Fine by me. I haven't seen it since the sqllite backout mentioned above.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.