Closed
Bug 617792
Opened 14 years ago
Closed 14 years ago
Updating from places branch to something else loses history if WAL is being used
Categories
(Toolkit :: Places, defect)
Toolkit
Places
Tracking
()
RESOLVED
DUPLICATE
of bug 617779
People
(Reporter: matjk7, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101208 Firefox/4.0b8pre Build Identifier: This probably hits testers more than real users. Reproducible: Always Steps to Reproduce: 1.Grab an not up-to-date places branch build 2.Navigate a while so new history is written 3.Check for updates and then apply the update Actual Results: All history is lost. Expected Results: History should be kept. If I shutdown the build and then update to a new trunk build (i.e through the installer) history is not lost, so I suspect the issue is that during the update process the contents of WAL journal are not actually written back to places.sqlite so when the new trunk build tries to read history it fails miserably.
Comment 1•14 years ago
|
||
dies the update bring you to a newer places branch build or to a mozilla-central build? which old builds did you test with? it's absolutely possible that some days older build does not correctly upgrade. did this produce a places.sqlite.corrupt file in your profile?
Comment 2•14 years ago
|
||
this is a dupe of bug 617779, and due to bug 617761. on nightly upgrade we upgrade to central and we hit the downgrade bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•