Ensure that the update success ping is sent before Firefox shuts down
Categories
(Toolkit :: Application Update, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr128 | --- | unaffected |
| firefox130 | --- | unaffected |
| firefox131 | --- | unaffected |
| firefox132 | --- | wontfix |
| firefox133 | --- | wontfix |
| firefox134 | --- | fixed |
People
(Reporter: bytesized, Assigned: ericchen647)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [fidedi-ope])
Attachments
(1 file)
We knew that the patch for Bug 1642039 did not ensure that UpdatePing.handleUpdateSuccess resolves before Firefox exits. We considered it low enough of a risk that we did not want to introduce that additional complexity into that already complex patch. But we should still fix this and make sure that we don't shutdown without allowing the function to run to completion.
A reasonable mechanism for this might be using a deferred task that is added as a shutdown blocker, like we do here. This would allow us to make UpdatePing.handleUpdateSuccess synchronous so that we wouldn't need to worry about awaiting on it at its call site.
Comment 1•1 year ago
|
||
Set release status flags based on info from the regressing bug 1642039
:erchen, since you are the author of the regressor, bug 1642039, could you take a look?
For more information, please visit BugBot documentation.
| Reporter | ||
Comment 2•1 year ago
|
||
erchen is on PTO. I think we will have someone else available to work on this soon.
Updated•1 year ago
|
Comment 3•1 year ago
|
||
Hey any update on someone looking at this for 132? 132 is going out to beta next week. I'm unclear how bad the S3 is here exactly.
| Reporter | ||
Comment 4•1 year ago
|
||
I'm not really that concerned with ensuring this is fixed before 133. It really shouldn't affect anyone with browser sessions longer than a few seconds. When it does happen, it does not affect anything user-facing - telemetry only.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 7•1 year ago
|
||
| bugherder | ||
Comment 8•1 year ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Comment 9•1 year ago
|
||
The patch landed in nightly and beta is affected.
:erchen, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox133towontfix.
For more information, please visit BugBot documentation.
Comment 10•1 year ago
|
||
Setting Fx133 to wontfix, based on comment 4 this does not need a release uplift.
Keeping NI open in case there's any disagreement.
Description
•