SQLiteDatabaseLockedException from GlobalHistory.add and GlobalHistory.update

NEW
Unassigned

Status

()

5 years ago
5 years ago

People

(Reporter: mfinkle, Unassigned)

Tracking

(Blocks: 2 bugs, {crash})

Firefox Tracking Flags

(Not tracked)

Details

GlobalHistory.add
https://crash-stats.mozilla.com/report/index/e7d11fcf-e006-448e-9bd0-8f8662131204

GlobalHistory.update
https://crash-stats.mozilla.com/report/index/8f121681-0faf-4624-a296-750702131130

Something is locking the DB and causing crashes. These two paths seem to appear quite a bit in the crash logs. We could just add some code to retry the operation once or twice.

This crash type is currently #3 on Fx26 (beta) and #4 on GA (Fx25).
Blocks: 752828
Keywords: crash
OS: Mac OS X → Android
Hardware: x86 → All
There's very little doubt in my mind that this is identical to Bug 947939.
Flags: needinfo?(rnewman)
(In reply to Richard Newman [:rnewman] from comment #1)
> There's very little doubt in my mind that this is identical to Bug 947939.

Agreed, but finding the root cause could be an epic adventure. Should we consider this bug and bug 947939 as ways to retry, and keep Fennec running, rather than crashing?
(In reply to Mark Finkle (:mfinkle) from comment #2)
> (In reply to Richard Newman [:rnewman] from comment #1)
> > There's very little doubt in my mind that this is identical to Bug 947939.
> 
> Agreed, but finding the root cause could be an epic adventure. Should we
> consider this bug and bug 947939 as ways to retry, and keep Fennec running,
> rather than crashing?

I would be open to attempting a retry, so long as we had some kind of mechanism for finding out whether retrying (or muffling) left the browser in any better state. No point in retrying if we're never going to be able to write to the DB ever again.

How many of these crashes are on builds that are submitting telemetry?
Flags: needinfo?(rnewman)
Blocks: 975024
You need to log in before you can comment on or make changes to this bug.