Open
Bug 1691370
Opened 5 years ago
Updated 4 years ago
Investigate the consequences of exiting the browser before the dispatcher is done processing it's tasks
Categories
(Data Platform and Tools :: Glean: SDK, task, P4)
Data Platform and Tools
Glean: SDK
Tracking
(Not tracked)
NEW
People
(Reporter: brizental, Unassigned)
References
Details
(Whiteboard: [glean-sdk:backlog][glean-js])
Glean.js is not being used yet, so we don't really know how much of a problem this is. We should investigate it once it starts being used.
When the browser is shutdown and there are still tasks enqueued as I understand it, the tasks will simply be dropped.
Special tasks such as sending a deletion-request ping are fine. We will check again in the next run. But what about recording a metric?
We should first check if this is a problem we can't overlook, before thinking about solutions. I am not sure it is something that will happen a lot and I see a potential rabbit hole. Let's avoid it if possible.
[UPDATE]
Well actually about ping submission, if the ping has not been collected, the submission task will also be lost.
|
Reporter | |
Updated•5 years ago
|
Whiteboard: [telemetry:glean-js:m?] → [telemetry:glean-js:backlog]
|
|
Reporter | |
Updated•4 years ago
|
Component: Glean.js → Glean: SDK
Whiteboard: [telemetry:glean-js:backlog] → [glean-sdk:backlog][glean-js]
You need to log in
before you can comment on or make changes to this bug.
Description
•