Closed Bug 257120 Opened 21 years ago Closed 21 years ago

Download manager history doesn't clear and downloading slowing as history list grows

Categories

(Toolkit :: Downloads API, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: r.russell, Assigned: bugs)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 The Firefox Download manager history doesn't clear and stalls browser as downloading slowed progrssively as history list grows. Reproducible: Always Steps to Reproduce: 1. Allow download history to become relatively large 2. Click Download manager clear 3. Observe firefox stall Actual Results: Firefox stalled. Uninstalled firefox and reinstalled with no change as old extensive list reemerged. Expected Results: Cleared download history. No prtoblems in clearing cache, cookies, etc
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040826 Firefox/0.9.1+ WFM I downloaded 20 files and pushed on the [clean up] button, it cleared DM , no problem
WFM: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10 Please reopen if you can reproduce with a current nightly.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Product: Firefox → Toolkit
If this helps, I have this issue as well. Though my downloads list is MUCH more extensive. WAY over 20 downloads. Every time I attempt to clear the histories in settings (I mainly use Firefox beta, btw) it freezes up the app, and doesn't ever appear to delete anything after finally force-closing and reopening. I can reproduce this every time. It ALWAYS happens.
Please verify if the hang happens when selecting ONLY Browsing and downloads history, or if you have other options selected when you clear history. Hangs of this type are more commonly caused by clearing the cache or cookies.
You need to log in before you can comment on or make changes to this bug.