Closed
Bug 843029
Opened 11 years ago
Closed 11 years ago
Add more retries to ensureDatabaseIsNotLocked
Categories
(Firefox for Android Graveyard :: Data Providers, defect)
Tracking
(firefox20+ fixed, firefox21+ fixed)
RESOLVED
FIXED
Firefox 22
People
(Reporter: mfinkle, Unassigned)
References
Details
Attachments
(1 file)
1.63 KB,
patch
|
lucasr
:
review+
blassey
:
review+
lsblakk
:
approval-mozilla-aurora+
lsblakk
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
If things go badly and the DB remains locked, the user is in trouble. Let's try a little harder to make sure the zombies have cleared up and any open DB connections have been closed.
Attachment #716016 -
Flags: review?(lucasr.at.mozilla)
Reporter | ||
Updated•11 years ago
|
Attachment #716016 -
Flags: review?(blassey.bugs)
Comment 1•11 years ago
|
||
Comment on attachment 716016 [details] [diff] [review] patch Review of attachment 716016 [details] [diff] [review]: ----------------------------------------------------------------- Looks good to me otherwise. ::: mobile/android/base/db/DBUtils.java @@ +67,5 @@ > + for (int retries = 0; retries < 5; retries++) { > + try { > + // Try a simple test and exit the loop > + dbHelper.getWritableDatabase(); > + break; I guess you meant 'return' here? Otherwise the log call you added below will always happen.
Attachment #716016 -
Flags: review?(lucasr.at.mozilla) → review+
Reporter | ||
Comment 2•11 years ago
|
||
(In reply to Lucas Rocha (:lucasr) from comment #1) > > + dbHelper.getWritableDatabase(); > > + break; > > I guess you meant 'return' here? Otherwise the log call you added below will > always happen. Good catch. That's what I get for adding the Log and not looking at the rest of the patch. Fixed locally.
Comment 3•11 years ago
|
||
Comment on attachment 716016 [details] [diff] [review] patch Review of attachment 716016 [details] [diff] [review]: ----------------------------------------------------------------- as Lucas already pointed out the only issue I see. I also wonder what other useful information we can log on failure, but that can be a follow up.
Attachment #716016 -
Flags: review?(blassey.bugs) → review+
Updated•11 years ago
|
status-firefox20:
--- → affected
status-firefox21:
--- → affected
tracking-firefox20:
--- → +
tracking-firefox21:
--- → +
Reporter | ||
Comment 4•11 years ago
|
||
Comment on attachment 716016 [details] [diff] [review] patch [Approval Request Comment] Bug caused by (feature/regressing bug #): User impact if declined: Testing completed (on m-c, etc.): Risk to taking this patch (and alternatives if risky): not a lot of risk. if this code is hit, we are in trouble already. the patch tries a little harder to bail us out. String or UUID changes made by this patch: none
Attachment #716016 -
Flags: approval-mozilla-beta?
Attachment #716016 -
Flags: approval-mozilla-aurora?
Comment 5•11 years ago
|
||
Comment on attachment 716016 [details] [diff] [review] patch Due to time constraints on getting FF20b1 for mobile builds kicked off, approving for uplift though it will still need to land on trunk/aurora.
Attachment #716016 -
Flags: approval-mozilla-beta?
Attachment #716016 -
Flags: approval-mozilla-beta+
Attachment #716016 -
Flags: approval-mozilla-aurora?
Attachment #716016 -
Flags: approval-mozilla-aurora+
Reporter | ||
Comment 6•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/b79b4213e3b2
Updated•11 years ago
|
Reporter | ||
Comment 7•11 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/5d609a1cf7be https://hg.mozilla.org/releases/mozilla-beta/rev/cf2437d4159e
OS: Android → Linux
Hardware: ARM → x86_64
Version: Trunk → Firefox 15
Updated•11 years ago
|
Comment 8•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/b79b4213e3b2
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•