User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20070219 Firefox/22.214.171.124 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20070219 Firefox/188.8.131.52 Upon opening a fresh browser, downloads work fine. When inactive for a few hours, starting a download or two will lock FireFox up and it will begin consuming 40-50% of CPU usage and anywhere from 500-1500 of memory (the amount of memory used is completely dependent on the amount of time since the lock up). This happens every single time, and I've went from 2.0 to 184.108.40.206 and now to 220.127.116.11 and it does the same thing. I haven't found anyone with similar problems, but I've not been able to remedy it. Reproducible: Always Steps to Reproduce: 1. Open fresh browser instance. 2. Download 100-200mb right away; this will work. 3. Wait anywhere from 2-6 hours, same instance of the browser open (possibly needing 5-10 tabs open, too) 4. Attempt to download anywhere from 2-5 files 20MB+ each at the same time. This will freeze the browser up, sometimes before even getting the 5th download started. Actual Results: Browser locked up and the process needed to be ended manually. Expected Results: Downloaded and saved the files like normal. No error messages when crashing, just a lock up.
Did you try cleaning up your downloads manager? See also http://kb.mozillazine.org/Downloads.rdf You could als try -safe-mode: http://kb.mozillazine.org/Safe_Mode_(Firefox)
works for me with Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9a6pre) Gecko/20070605 Minefield/3.0a6pre ID:2007060504 [cairo] David, do you still crash with a latest release like Firefox 18.104.22.168 ? If so, could you provide a Talkback ID (http://kb.mozillazine.org/Talkback)
Whiteboard: CLOSEME - 06/18
Version: unspecified → 2.0 Branch
-> incomplete- missing feedback and still waiting for talkback ID
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.