Open Bug 1890278 Opened 6 months ago Updated 1 month ago

_importJSONDump sometimes seem to escape its shutdown blocker

Categories

(Firefox :: Remote Settings Client, defect)

defect

Tracking

()

People

(Reporter: jstutte, Unassigned)

References

Details

From bug 1813353 it seems there can be situations where we enter shutdown while _importJSONDump is running. We might want to consider to harden this with a shutdown blocker.

See Also: → 1813353

Jens, it seems that we already have a shutdown blocker...

_importJSONDump calls the worker method RemoteSettingsWorker.importJSONDump:
https://searchfox.org/mozilla-central/rev/c09764753ea40725eb50decad2c51edecbd33308/services/settings/RemoteSettingsClient.sys.mjs#966-969

And we have a shutdown blocker that waits for worker callbacks to have finished:
https://searchfox.org/mozilla-central/rev/c09764753ea40725eb50decad2c51edecbd33308/services/settings/RemoteSettingsWorker.sys.mjs#182-219

I don't know where to start to debug this :/

Summary: _importJSONDump does not block shutdown → _importJSONDump sometimes seem to escape its shutdown blocker

Could there be cases/races where gShutdown is never set and the after-shutdown check here will not work?

You could try to substitute the gShutdown checks with Services.startup.isInOrBeyondShutdownPhase(Ci.nsIAppStartup.SHUTDOWN_PHASE_APPSHUTDOWN), FWIW.

See Also: → 1815163
See Also: → 1808168

The severity field is not set for this bug.
:leplatrem, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(mathieu)
Severity: -- → S1
Flags: needinfo?(mathieu)
Priority: -- → P1

Per https://wiki.mozilla.org/BMO/UserGuide/BugFields#bug_severity:

S1 (Catastrophic) Blocks development/testing, may impact more than 25% of users, causes data loss, likely dot release driver, and no workaround available

Is that the correct severity for this bug?

Flags: needinfo?(mathieu)

Oops. No. Sorry. Thank you for the heads up

Severity: S1 → S3
Flags: needinfo?(mathieu)
Priority: P3 → --
You need to log in before you can comment on or make changes to this bug.