User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:18.104.22.168) Gecko/2008070208 Firefox/3.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:22.214.171.124) Gecko/2008070208 Firefox/3.0.1 This may be a memory leakage problem. MobileMe behaves well using Apple's Safari browser, but does not play well with FF3. Take a look at this discussion thread for more: http://discussions.apple.com/thread.jspa?threadID=1605288&tstart=0 Reproducible: Always Steps to Reproduce: 1. Log into MobileMe service at www.me.com. 2. Add/delete/modify an event in the calendar. 3. Within a few seconds FF3 is frozen.
Does the freeze go away after a short time?
I think I waited a few minutes, and it did not unfreeze. But last night I was able to work in MobileMe calendar without trouble from FF3. If I get another freeze, I'll keep the browser open and try to wait it out.
Has this issue appeared again? You can also try Safe Mode.
I'm seeing this here as well. Mac OS X 10.5.5, Nov. 13 Minefield. Will attach sample from Activity Monitor during hang and crash report.
ok, those reports alone aren't usable. ted has outlined a process "somewhere" by which you could calculate correct stack traces. if you're interested (and especially if you know perl/python and want to make a useful parser to automatically do it), that'd be great. otherwise this bug w/o a stack based on a debug build is unlikely to go anywhere.
https://wiki.mozilla.org/Manually_Parsing_Breakpad_Symbol_Files I wouldn't recommend it to humans, though.
Reporter, please retest with Firefox 3.6.12 or later in a fresh profile (http://support.mozilla.com/kb/Managing+profiles). Also update your plugins (flash, adobe reader, java, quicktime, silverlight, etc.) Go to the developer's website and download the latest version from there. If you no longer see this issue, please close this bug as RESOLVED, WORKSFORME. If you do see the bug, please post a comment.
Whiteboard: [CLOSEME 2010-12-01]
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.