157680 - Installer should clear download history, if it exceeds a certain size

Status: VERIFIED DUPLICATE of bug 251337

(SeaMonkey :: Download & File Handling, defect)

Description

[Martin Wehner]

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT)
BuildID:    20020716

To be done for mozilla1.1final:

I uninstalled mozilla 1.0 before I installed mozilla 1.1.
But downloads.rdf was left unchanged on my system and still
causes sluggish behaviour when the download manager is opened
or when I download files or images.
I would suggest that the next version of the installer deletes
downloads.rdf if it exists and its size exceeds a limit.

John Morrison (Netscape) pleased me to open a bug for this in
mozilla 1.1final.
This bug refers to bug 157491 which was reopened by him.


Reproducible: Always
Steps to Reproduce:
1. uninstall mozilla 1.0
2. install mozilla 1.1


Actual Results:  downloads.rdf remains unchanged on the system and
if this file is of huge size it still causes sluggish behaviour when the
download manager is opened or when I download files or images
(regardless to the update from 1.0 to 1.1).


Expected Results:  I would suggest that the next version of the installer
deletes downloads.rdf if it exists and its size exceeds a limit.

Comment 1

[Dimitrios]

Invalid summary (seems more like a meta bug for Mozilla developers/drivers).
Changing to "Download history should be cleared when installing a new release,
if exceeds a certain size". 
Imho, this is a bloated way of fixing the huge download history file issue.
Better fix bug 141794 or bug 132755... 

Comment 2

[Wesha]

The issue should be fixed, this or that way, but I strongly beleive it's a dupe.
Please keep up with the discussion on the bug 132755.

*** This bug has been marked as a duplicate of 132755 ***

Comment 3

[Jason Bassford]

This bug is not a duplicate of bug 15760.  That bug is about removal based on
TIME parameters.  This bug is about removal based on the SIZE of the list.  Bug
15760 doesn't have anything to do with only keeping X number of items...

Comment 4

[Jason Bassford]

Apologies.  This bug is not a duplicate of bug 132755.

Comment 5

[Wesha]

Jason, I don't see why should we keep TWO separate bugs for a SINGLE issue,
which should sound like "Download list should not grow endlessly". Wether we do
it by erasing the list, or trimming it by date, or by size, or whatever, is
exactly what is discussed in bug 132755. Why not going there and expressing your
opinion (and closing this bug to minimize database clutter, too)?

Comment 6

[Dimitrios]

wesha, I think it's better to leave that kind of resolution to the bug owner. I
agree with you that there are better ways to keep history small (than this one)
but we are not those who make the decisions.

Comment 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 8

[Robert Kaiser]

Move to toolkit download manager made this a dupe of bug 251337.