334946 - Search fails with javascript error

Status: RESOLVED INVALID

(Firefox :: Search, defect)

Description

[Mats Åhlberg]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060420 Minefield/3.0a1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060420 Minefield/3.0a1

When i press enter in the quicksearch i get this in the javascript console.

I have the same problem even when running in safe mode.

This appears in the javascript console when i press enter in search.

Error: this._formHistSvc has no properties
Source File: chrome://browser/content/search/search.xml
Line: 320

Reproducible: Always

Steps to Reproduce:
1.Enter search data in google-seach
2.Press enter.
3.

Actual Results:  
Nothing happen except a javascript error

Expected Results:  
Go to google and search for the data

Comment 1

[Ria Klaassen (not reading all bugmail)]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060420 Minefield/3.0a1
WFM and no error with this build: 1.9a1_2006042102

Comment 2

[Mats Åhlberg]

I located the problem but it is quite weird.
I removed my profile and created a new one.
Started firefox and the search bar worked.
Then i added files from my old profile one by one and
relaunched firefox etween each.

When i added formhistory.sqlite the search stopped working.
I removed formhistory.sqlite again and then search worked again.

Comment 3

[:Gavin Sharp [email: [e-mail]]]

Ah, that's not so weird: this might be bug 334793. Are there any other JS exceptions? I'd imagine you'd see the GetService ones described in bug 334793.

Comment 4

[Mats Åhlberg]

No i don't see any other javascript errors.
And i could not reproduce bug 334793 either.

Comment 5

[Joshua]

This can be fixed ( normaly ) with a simple uninstall and reinstall. I have heard of this 2 times before this.

Comment 6

[Stephanie Daugherty [:sdaugherty]]

I'm not sure this is going to be reproduceable for anyone at this point, since it sounds like the formhistory.sqlite was somehow corrupted.
At least this would be solved by the standard advice to create a new profile.
Closing this as INVALID for now, if it happens again please reopen and we'll take another look.