User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5 Every time on that page(http://www.twiddla.com/) Firefox starts using 100% of one of the cores. Increases memory footprint dramatically(doubles from 100 MB to 200-250 MB). Happens every time that page is loaded. Firefox 188.8.131.52 Does NOT have that problem. (I have NoScript intalled, with setting to allow Current Top Level Sites by default) Reproducible: Always Steps to Reproduce: 1. Start Firefox 3 B5 2. Navigate to: http://www.twiddla.com/ 3. Click "Try it now in the sandbox" 4. Sit back and wait. Actual Results: Freezes completely. All windows of Firefox freeze. Expected Results: Opens a virtual whiteboard application(DHTML + AJAX)
Works for me. 1. Tested first with clean b5 (Vista) and no add-ons, no issues, could play around with the web-application (quite advanced app) 2. then installed noscript (latest version, 1.5.6), with default settings an empty page was opened in step 3, ok I assume(?) 3. Then changed setting in no-script to "temporarily allow top-level sites by default" and the application worked fine again. Do you have the latest version of noscript? Have you tested with a clean profile? Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
Does the bug happen without noscript? This WFM as well, and if noscript is causing the problem, mao can fix that or file against the root cause if there is one...
Reporter, are you still seeing this issue with Firefox 3.6.8 or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
No reply, INCOMPLETE. Please retest with Firefox 3.6.10 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.