crashreporterNetworkBackend retries Glean deletion request ping indefinitely when telemetry endpoint is DNS blocked; each retry registers as an app instance and pollutes macOS Dock recent-apps.
Categories
(Toolkit :: Crash Reporting, defect)
Tracking
()
People
(Reporter: notpentadactyl, Unassigned)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
|
53.75 KB,
image/png
|
Details |
macos-firefox-ghost-icons.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:153.0) Gecko/20100101 Firefox/153.0
Steps to reproduce:
I do not know, but should be easy to reproduce by blocking incoming.telemetry.mozilla.org via DNS.
What made it stop: rm ~/Library/Application\ Support/Firefox/Crash\ Reports/glean/deletion_request/<uuid>.
Actual results:
Firefox seems to retry Glean deletion request ping indefinitely when telemetry endpoint is DNS blocked.
$ dig incoming.telemetry.mozilla.org +short
$
This causes Firefox app icons (two in my case) to appear in the "recent applications" section of the macOS Dock (see attached screenshot).
This happens every time I (re)start Firefox after ~1 minute or so.
Expected results:
No Firefox app icons should appear in the "recent applications" section of the macOS Dock.
I already have Firefox set to "Keep in Dock".
|
||
Comment 1•28 days ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Telemetry' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•28 days ago
|
||
The retry behaviour is desired and not something we're likely to be able to change, alas. If you opt out of data collection, Mozilla's servers need to be told so we can delete any stuff we might've collected up 'til then. If we can't submit the "deletion-request" ping because of a failure that might be transitory, we need to keep trying.
Moving to Crash Reporting in case there's something we can do about the icon appearing in the dock, or in case there's something about the data opt-out that we can finesse here (maybe this sort of case could be avoided by ensuring the data opt-out is known before Glean is init?).
|
|
||
Comment 3•13 days ago
|
||
The severity field is not set for this bug.
:gsvelto, could you have a look please?
For more information, please visit BugBot documentation.
|
||
Comment 4•4 days ago
|
||
The icon shouldn't appear at all, this is bug 2033350 (which is mostly a superficial tracking bug for crashreporting; the real bug is bug 1829423).
I'm going to make this a higher severity than bug 2033350 because, in this case, it is a much more user-visible and troublesome behavior. I've recently followed up on bug 1829423 to get a fix there; hopefully it won't be much longer.
Description
•