User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux 18.104.22.168-desktop-1mdv; X11; x86_64) KHTML/3.5.7 (like Gecko) Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:22.214.171.124) Gecko/20070914 Mandriva/126.96.36.199-1.1mdv2008.0 (2008.0) Firefox/188.8.131.52 as well as Mozilla/5.0 (X11; U; Linux i686; en-US; rv:184.108.40.206) Gecko/20070208 Mandriva/220.127.116.11-12mdv2008.0 (2008.0) Firefox/18.104.22.168 When trying to browse the site, Mozilla stops respomnding, the system is busy in 100% and heavy hdd operation. probably the only way out is hard reset. even ctrl+alt+bspce do not work. For both 32 and 64 bit version the effect is the same, while konqueror and opera work properly. The windows version of Mozilla doesn't crash on that site. Reproducible: Always Steps to Reproduce: 1. browse http://rokor1.pl.tl/ 2. 3. Actual Results: Mozilla doesn;t respond, system busy 100% and not responding, heavy hdd operation Expected Results: show the site as other browsers do
Created attachment 297954 [details] Testcase (WARNING: hangs the entire desktop) This is a standalone and somewhat reduced version of the URL.
Assignee: nobody → general
Status: UNCONFIRMED → NEW
Ever confirmed: true
Product: Firefox → Core
QA Contact: general → general
Whiteboard: [sg:dos] out of memory
Version: 2.0 Branch → Trunk
mw, do you have Kerio Personal Firewall ? From <http://lucisandor.info/blog/?p=242> it looks like it is inserting the "popup" blocking code. I don't have a problem with the "blocking" script removed except for the numerous parsing errors for top and the fact that the animation is set to run every 1ms. Try disabling the popup blocking on the firewall since you don't need it with Firefox anyway. I look at the script more to find out the cause of the "hang".
Get a terrible hang on Windows XP.
Regression window of the hang on Windows is http://bonsai.mozilla.org/cvsquery.cgi?module=PhoenixTinderbox&date=explicit&mindate=2006-02-07+04%3A00&maxdate=2006-02-07+13%3A00
Today http://rokor1.pl.tl/ didn't hang anymore, so I did a re-check for the regression range, this time with the testcase, but the range was correct.
Is this still an issue?
Seems to work fine now, please file a new bug if this is still a problem.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.