Closed Bug 1464341 Opened 8 years ago Closed 8 years ago

Error: Synchronously loading the add-ons database (resource://gre/modules/addons/XPIDatabase.jsm:1386:17)

Categories

(Toolkit :: Add-ons Manager, defect)

Product:
Toolkit
Component:
Add-ons Manager
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1462681
Tracking Flags:
Tracking Status
firefox61 --- unaffected
firefox62 --- affected

People

(Reporter: whimboo, Unassigned)

References

Details

Since a couple of days I see delays during startup of Nightly builds most likely caused by the following error: > [task 2018-05-25T03:32:12.432Z] 03:32:12 INFO - PID 2738 | 1527219132412 addons.xpi-utils WARN Error: Synchronously loading the add-ons database (resource://gre/modules/addons/XPIDatabase.jsm:1386:17) JS Stack trace: syncLoadDB@XPIDatabase.jsm:1386:17 > [task 2018-05-25T03:32:12.434Z] 03:32:12 INFO - PID 2738 | checkForChanges@XPIProvider.jsm:2775:9 > [task 2018-05-25T03:32:12.436Z] 03:32:12 INFO - PID 2738 | startup@XPIProvider.jsm:2324:25 > [task 2018-05-25T03:32:12.440Z] 03:32:12 INFO - PID 2738 | callProvider@AddonManager.jsm:205:12 > [task 2018-05-25T03:32:12.443Z] 03:32:12 INFO - PID 2738 | _startProvider@AddonManager.jsm:653:5 > [task 2018-05-25T03:32:12.447Z] 03:32:12 INFO - PID 2738 | startup@AddonManager.jsm:812:9 > [task 2018-05-25T03:32:12.451Z] 03:32:12 INFO - PID 2738 | startup@AddonManager.jsm:2864:5 > [task 2018-05-25T03:32:12.452Z] 03:32:12 INFO - PID 2738 | observe@addonManager.js:66:9 Here an example: https://treeherder.mozilla.org/logviewer.html#?job_id=180158550&repo=autoland&lineNumber=26871-26881 This failure is visible for each and every start of Firefox.
As it looks like this depends on the changes from bug 1461140 which landed 8 days ago. Is this warning expected? It kinda blows-up the log and is annoying.
Depends on: 1461140
Flags: needinfo?(kmaglione+bmo)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Flags: needinfo?(kmaglione+bmo)
You need to log in before you can comment on or make changes to this bug.