Closed Bug 623865 Opened 14 years ago Closed 14 years ago

Search with Google or Yahoo freeze Beta 8

Categories

(Firefox :: General, defect)

3.6 Branch
x86
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: georges.bray, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 (.NET CLR 3.5.30729) Since Yesterday I am unable to make any search with Firefox Beta 8 it freezes Firefox. The only thing I can do is to close Firefox but I can't reopen it, a message is saying that Firefox is in use. The only solution ia complete reboot. Reproducible: Always Steps to Reproduce: 1.In the search bar with Google or Yahoo type for example "Exercices sur la loi des mailles" or anything else 2.Results appear but even waiting several minutes it is impossible to do anything ... 3. Actual Results: Results appears but Firefox is working and working and the only solution is a reboot
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.14pre) Gecko/20110106 Namoroka/3.6.14pre works for me. Please try if it works fine in safe mode or try by creating a new profile. https://support.mozilla.com/en-US/kb/Safe+Mode https://support.mozilla.com/en-US/kb/Managing+profiles#Creating_a_profile.
08/01/2011 7:00 A) It works fine in safe mode B) I don't try to create profiles because we are two to use the laptop C) This problem appears say thursday may be wednesday but before it was working well. I don't explain this change
I can confirm this bug. I actually came across this looking to see if it had already been reported. It doesn't work in safe mode for me either, will try a new profile
Also, I'm using XP, not 7
Correction - it will work in safe mode. I'm going to try re-enabling addons and see if I can point to a specific one.
I'm sorry to keep spamming everyone with emails, but I can safely say that McAfee Site SiteAdvisor is the addon causing this problem.
Confirm that McAfee siteadvisor 3.3 extension is the culprit on Windows Vista
Confirm that McAfee siteadvisor 3.3 extension is the culprit on Windows Vista
May be but everything was working well say before at most 48h before my first post and it is always working with Firefox 3.7. For me the problem is not Mc Afee but Beta 4.0 Beta 8 and a very recent modification which is perhaps not compatible with site Advisor.
We have got Firefox 4.0 Beta 10. I was thinking that the problem would be solve with this new version but I was wrong it's exactly the same. Why is Firefox 3.6 working perfectly well in the same environment including Mc Afee and Mc Afee Security Scan Plus and Site Advisor Plus. Why, may be it works without Site advisor plus but for me it is not a complete answer, it must work like Firefox 3.6 with it.
Version: unspecified → 3.6 Branch
Confirm that McAfee SiteAdvisor 3.3 extension is the culprit on Windows 7 FireFox4 Beta11
georges, so if you disable site adviser does the problem go away?
Bump for comment 12. If disabling the site advisor (and then restarting Firefox for the change to take effect) helps, it would be useful to know what version you are using (for bug 637542). In which case, please can you go to the page "about:support" (type it without quotes in the address bar) and paste the contents of the extension section as a reply here. Thanks!
McAfee SiteAdvisor 3.3 false {B7082FAA-CB62-4872-9106-E42DD88EDE45} I haven't tested it yet on the current version of Firefox. Will do soon and post results.
Still doesn't work correctly. Once the Google page loads, firefox completely freezes.
If the problem goes away in safe mode, it's very likely caused by an extension. Disable all of your extensions, restart Firefox and try again. If that works, re-enable them one at a time (restarting Firefox after doing so, for the change to take effect) until you can narrow down which is causing it.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.