User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 GTB7.1 ( .NET CLR 3.5.30729) Build Identifier: http://www.mozilla.com/en-US/firefox/4.0b9/releasenotes/ Downloaded Firefox 4 Beta 9 and searched google.com. No search result is clickable. The browser hangs. I am still able to scroll up and down but that’s it. If I close the program it does not ever leave my Task Manager (at least not for 10 minutes; after that I forcibly terminated it). Reproducible: Always Steps to Reproduce: 1. Open Firefox. 2. Search for anything on Google. 3. Actual Results: As detailed: no result is clickable, though the window can be scrolled. Expected Results: Should be able to click on any link. The mouse pointer stays as an arrow. Firefox does not know something is up so no Crash Reporter comes up.

Please try http://support.mozilla.com/en-US/kb/Safe+Mode

Do you have McAfee Site Advisor installed?

Hi Matthias and Tim: Thank you both. I do have SiteAdvisor installed. I’ll give it a shot next time with it removed.

Jack -> Any update?

Closing bug as INVALID - if you are still experiencing this issue or have more information to provide feel free to post back here and we can re-open the bug. You can also get assistance by visiting the Firefox help site -> http://support.mozilla.com/en-US/kb/Ask+a+question

Jack, did disabling McAfee Site Advisor help? If so, it would help to know what version you were using, for working out a version blocklist range in bug 637542. To find out the version, you can 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.

Hi Ed: yes, it did. In fact, every time it opened with McAfee SiteAdvisor installed and a Google page was one of the tabs, the whole program would freeze. Here are those details: McAfee SiteAdvisor 3.3 true {B7082FAA-CB62-4872-9106-E42DD88EDE45} I am now on 4 Beta 13 and the error continues to exist. I had apologized to Tim off-list: I had a business trip in between those last two dates and was unable to test.

Thanks for the update - the version/ID will help work out what range needs to be blocked (which will happen in bug 637542). As for it still not working in b13pre, that's unfortunately expected, since the problem needs to be fixed by McAfee, rather than Mozilla/Firefox. McAfee are reported to be working on a fix however.

Reopening since now in the McAfee section, so something for them to sort out.

Is this still an issue with that latest version of Firefox and McAfee SiteAdvisor?

Hi Tim: all appears to be fine on Firefox 6.0.1, thank you.

Thanks for the update :-)