Status

()

For bugs in Firefox Desktop, the Mozilla Foundation's web browser. For Firefox user interface issues in menus, bookmarks, location bar, and preferences. Many Firefox bugs will either be filed here or in the Core product. Bugs for developer tools (F12) should be filed in the DevTools product. (more info)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1
I tried several of the download pages on download.cnet.com and they all use a lot of processing power and then the window simply shuts down. Did not happen with Firefox 3.1. I tried it in Save mode with all add-ons disabled, same effect
Reproducible: Always
Steps to Reproduce:
1. Go to http://download.cnet.com/Process-Explorer/3000-2094_4-10223605.html?dl-blog&tag=mncol;txt
2.
3.
Actual Results:
Firefox 3.5.1 closes window after some time using one processor core to 100%

(In reply to comment #5)
> Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.1pre) Gecko/20090720
> Shiretoko/3.5.1pre
>
> No problem here with the site. Can you try the following trouble-shooting
> options:
>
> - Firefox's safe-mode to exclude extension/theme problems
> - a new profile
I made a new profile, installed all my add-ons and it worked fine. But then I found the reason for the problem: I do NOT allow cookies in my default profile. As soon as I allowed it for download.cnet.com it worked fine.
So the problem is obviously the function on the cnet website. Still I find the behaviour of Firefox kind of buggy.
Thanks for the help.
> - a reinstall in a new empty folder
>
> http://support.mozilla.com/en-US/kb/Safe+Mode
> http://support.mozilla.com/en-US/kb/Basic+Troubleshooting#Make_a_new_profile

This won't be a cookie bug... my guess is some bad javascript that's creating an infinite loop or somesuch, as a result of not being able to set cookies. Though it must be a bit more complex than that, given it ends with a crash rather than a slow script dialog.

Summary: Pages on download.cnet.com use one core to 100% and the windows closes after some time → download.cnet.com - with cookies disabled, uses one core to 100% (slow/freeze/hang) and the window closes after some time

I copied the page to my local disk. I started Apache. I added the <base href="..."> tag, disabled all cookies and loaded the page via 127.0.0.1.
It doesn't reproduce that way. There is no XHR. I see that both with original site and copy. So, what could be the difference? A real domain name????
Anyone any ideas? This is spooky. This way I can't reduce it.
Lucas

Created attachment 393154[details]
Website files
I tried to see where the hang was occurring but couldn't.
Anyways, the debugger was complaining about line 114 of the CookieXfer.html file (contained in the attached) returning no value, just before the hang.

Some notes.
The CookieXfer.htm is loaded by <iframe> if you have cookies disabled. If cookie is enabled, it will not appear on the site (the server probably reacts on the http header info).
The CookieXfer.htm is loaded 4 times in the attachment of #15. Probably, only 1 was intended.
The path of oreao.js in the CookieXfer.htm is not correct (bug in saving). Remove the first part of the path.
But that doesn't help to reproduce it locally. There are still some things that are necessary to reproduce it locally. Don't know what the CookieXfer.htm file is doing. Probably to do an alternative when cookies are disabled, but I don't know what.
Probably some paths have to be corrected, to get reproduced locally. But then I need to know what it is doing.
Maybe a bisect could help (if it doesn't reproduce with older versions). Then we have some clue where to look.

/home/processor/stackwalk/bin/stackwalk.sh returned no header lines for reportid: 68970976; No thread was identified as the cause of the crash; No signature could be created because we do not know which thread crashed; /home/processor/stackwalk/bin/stackwalk.sh returned no frame lines for reportid: 68970976; /home/processor/stackwalk/bin/stackwalk.sh failed with return code 1 when processing dump 4a8c96c0-04b7-4b1c-8dc8-b40272091031