Closed Bug 97182 Opened 23 years ago Closed 23 years ago

AutoConfig is created twice as part of netscape.cfg reading

Categories

(Core :: Preferences: Backend, defect)

Product:
Core
Component:
Preferences: Backend
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla0.9.8

People

(Reporter: mitesh, Assigned: bnesse)

References

Details

Right now, autoconfig object is created inside readconfig() in nsPrefSerice.cpp.
As a result of a fix for bug 92447, the readconfig will be called again when
resetprefs() happens in profile migration case or runtime profile switching (in
the future). We need to be able to release autoconfig and restart autoconfig
object with the new values which is not the case right now.
QA Contact: sairuh → lrg
Depends on: 92447
*** Bug 87661 has been marked as a duplicate of this bug. ***
*** Bug 86688 has been marked as a duplicate of this bug. ***
How abt we use do_GetService instead do_CreateInstance. I think that will make
sure that the AutoConfig is created as a singleton object.
Blocks: 113387
mitesh is no longer with us. reassigning to default module owner. bug 113387
tracks the original list of mitesh bugs
Assignee: mitesh → bnesse
QA Contact: lrg → sairuh
This will be fixed by the patch in bug 89137.
Depends on: 89137
Patch for bug 89137 has landed. This is now fixed.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla0.9.8
rodney, luke, would you like to verify this one? thx!
QA Contact: sairuh → rvelasco
Brian, i am not quite sure on how to go about testing this, since the extra
process creation is pretty invisible.  Any suggestions?
QA Contact: rvelasco → lrg
It's really a code based thing. You won't be able to verify it in any visually
obvious way. I guess I could show you the code which keeps it from creating
multiple instances...
You need to log in before you can comment on or make changes to this bug.