appreg (unix registry) file grows without bound if you create and remove a single profile

RESOLVED EXPIRED

Status

Core Graveyard
Profile: BackEnd
RESOLVED EXPIRED
15 years ago
2 years ago

People

(Reporter: William Bardwell, Unassigned)

Tracking

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       
Build Identifier: 1.5

I made a program that creates and removes a single profile name,
updating the registry between each.
And the appreg file just grows and grows, even though the amount
of meaningful data isn't changing.  This is unfortunate behavior,
and means that writting mozilla based programs which only really
want a temporary profile pretty much requires leaving the temporary
profiles around for ever, or face an eventual major failure when the
registry file gets too big.

Reproducible: Always
Steps to Reproduce:
  nsCOMPtr <nsIProfileInternal> profile_manager =
    do_GetService(NS_PROFILE_CONTRACTID, &rv);
nsString junk_profile;
junk_profile.AssignWithConversion("bardwell-junk");
profile_manager->UpdateRegistry(nsnull);
for (int j = 0; j < 100000; ++j) {
profile_manager->CreateNewProfile(junk_profile.get(),
nsnull, nsnull, PR_TRUE);
profile_manager->UpdateRegistry(nsnull);
profile_manager->DeleteProfile(junk_profile.get(), PR_TRUE);
profile_manager->ForgetCurrentProfile();
profile_manager->UpdateRegistry(nsnull);
if (j % 1000) {
    printf("%d\n", j); fflush(stdout);
}
}

Actual Results:  
my appreg file went from 7k to 300k (and I stoped it early)

Expected Results:  
appreg file should reach a steady state size where it stops
getting bigger.
Assignee: general → nobody
Component: Browser-General → Profile Manager BackEnd
QA Contact: general → core.profile-manager-backend

Comment 1

15 years ago
Isn't this bug 10210 ? See bug 109739 comment 26
We're not fixing the libreg format, we want to kill it. See bug 174522
Depends on: 174522
No longer depends on: 10210
Depends on: 10210
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
(Assignee)

Updated

2 years ago
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.