Closed Bug 1144656 Opened 9 years ago Closed 6 years ago
DB lock timeout too short
Well it's just a warning for the sake of avoiding regressing the bad locking issues we had in the past, and in case it may happen, being able to track the root cause. The value of 30 secs was just a value I mostly picked to be good enough on startup of low devices, and still exposing quite fastly the locking issue when it happened. A bad clock may also trigger it, as in bug 1119727
Having had to use the emulator-kk builds recently too, I agree that it would be nice to parametrize this for those builds. It looks like SettingsRequestManager.jsm is not currently preprocessed, and preprocessing JS files is horrible, so it seems like a pref in the already-preprocessed b2g/app/b2g.js for this situation would be ideal. The pref could just be read at init time with the other prefs in the file (no need to update in real-time to changes to the pref.)
I second what :gerard-majax said in Comment 1.
Looks like bug 1119727 are going to provide a way to configure the timeout threshold.
See Also: → 1119727
Cleaning up Device Interfaces component, and mass-marking old FxOS bugs as incomplete. If any of these bugs are still valid, please let me know.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.