Open Bug 715315 Opened 8 years ago Updated 8 years ago
Ensure source Firefox profile is not in use during migration
Copying some databases or files while they are in use may lead to incomplete/inconsistent data. The migrator should ensure that the profile or specific files are not in use. Ideal solution would be to migrate after acquiring a profile lock if this can be done safely.
I'm not sure how you could trigger such a situation. The Firefox option, in the wizard, is only available if --migration is used. We don't care about this "use case". The only other way to invoke the Firefox migrator is by using the Reset Profile feature, which restarts the browser and imports the current profile. One thing you may want to do is to set selectedProfile==currentProfile in the reset use case. That would ensure the right profile is imported after restart.
Severity: enhancement → minor
What about making the Firefox profile migration code actually migrate the data instead of simply copying over the files?
(In reply to Michael Kaply (mkaply) from comment #2) > What about making the Firefox profile migration code actually migrate the > data instead of simply copying over the files? would be slow and hard to maintain, it's hard enough to maintain 3 migrators that migrate just some data.
You need to log in before you can comment on or make changes to this bug.