Closed
Bug 610205
Opened 15 years ago
Closed 15 years ago
Update process won't complete successfully if the cache was cleared
Categories
(Toolkit :: Application Update, defect)
Toolkit
Application Update
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: idr.ugoy, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101106 Firefox/4.0b8pre
Build Identifier:
I use an extension that clears cache by timer. So, in case Fx popped up that there is a newer version available and I click to download it - it gets downloaded but won't get applied until I restart the browser. Sometimes I am busy reading an interesting article, and I postpone browser restart. If during my reading the cache got cleared by the extension, then I can't re-download the update and all I can is to click "restart the browser" button. And after it restarts - there is no update progress bar shown, it just loads the browser and says there was a problem and the update failed.
Reproducible: Always
Steps to Reproduce:
1
Comment 1•15 years ago
|
||
You should tell us more about which type of Cache the extension is clearing. Can you upload the extension somewhere so it can be used for testing purposes? Also I don't see a relationship to bug 315278 for now.
Please go to about:config and enable app.update.logs, so messages will appear in the Error Console which could tell, what's now working.
No longer blocks: 315278
Version: unspecified → Trunk
| Reporter | ||
Comment 2•15 years ago
|
||
Seems like it happens from time to time. Today I couldn't reproduce this bug. Now I even doubt it is connected with clearing cache. I'll try to reproduce it with the next updates.
| Reporter | ||
Comment 3•15 years ago
|
||
and there is no app.update.logs in the about:config. Or should I create it ("true" boolean I suppose?)?
Comment 4•15 years ago
|
||
Sorry, it should read app.update.log.
| Reporter | ||
Comment 5•15 years ago
|
||
I did clear the cache after downloading the update, did vacuuming places.sqlite and even tried to enter Private Mode and then quit it. But the update process finished successfully, so I mark this bug as WORKSFORME, until I meet that bug again and if I get know what's the reason.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Updated•15 years ago
|
Resolution: WORKSFORME → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•