User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/20100722 Firefox/3.6.8 ( .NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/20100722 Firefox/3.6.8 ( .NET CLR 3.5.30729) with each new update firefox has gotten worse it now freezes or locks up. i'm running win xp pro ver 5.1 firefox 3.6.8 roadrunner business as the isp Reproducible: Always Steps to Reproduce: just using the browser is the problem Actual Results: freeze, lockup Expected Results: not to do the above at all i don't have my own computer and i must use the library system where there are time limits on computer use - can't afford the lost time
Please contact the support under http://support.mozilla.com This is the developer part of mozilla and we need much more detailed information and that includes debug information that you can only get with installing a debugger. General feedback isn't useful for our developers
as i said before i have NO OTHER ACCESS to the 'net other than the library - hence i can't do anthing about the computers there. the problem started when i upgraded to ff 3.6.6 and the problem persisted after upgrading to 3.6.8 which tell me you did noting about the issue. i am NOT the only one with this problem - you NOT even reading your own forum if you not aware of this problem. a lot of people are getting **** off and are dropping firefox and the bad publicity is is spreading all over the 'net. see here: http://sphotos.ak.fbcdn.net/hphotos-ak-snc4/hs043.snc4/34513_1545392641889_1447221632_31513430_6711388_n.jpg is that a hint?
I saw reported freezes from day 1 (10 years ago) that I help here in bugzilla There are more reported freezes with 3.6.4 because there seems to be issues with OOPP. I don't read Forums because there is not much time left doing that. I spend my free time here in bugzilla. And of course, that are not my Forums because I'm only a user like you. Reporting it's crashing always or it's freezing always isn't enough and is useless. Don't you think that the developers are using their own product and would fix such issues really fast ? It can't be reproduced by the developers and by me and most other people. The developer need exact steps to reproduce or a stack trace and I assume that you already did the basic troubleshooting with a new profile and tested without addons. Attaching (not post) a stacktrace generated using Windbg might help. -> https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg