Closed Bug 1644252 Opened 5 years ago Closed 5 years ago

Clarify in code and docs that accumulations in GeckoViewStreamingTelemetry's SendBatch could deadlock

Categories

(Toolkit :: Telemetry, task, P1)

task
Points:
1

Tracking

()

RESOLVED FIXED
mozilla80
Tracking Status
firefox80 --- fixed

People

(Reporter: chutten, Assigned: chutten)

Details

Attachments

(1 file)

As :froydnj mentioned today on Slack, SendBatch could deadlock if something inside it decided to accumulate.

Most of it is framework level stuff like nsTArray's SwapElements but it isn't unreasonable that NS_DispatchToMainThread might one day decide to accumulate something and stream it over the GV Streaming bridge for Fenix reporting.

At this point I don't think there's much we'll want to do in code to prevent it (there are multiple barriers to adding measurements that would cause the deadlocks, and Project FOG will provide a better way to get metrics from Gecko out via Fenix's Glean in the medium term) but let's at least document the possibility.

Assignee: nobody → chutten
Status: NEW → ASSIGNED
Points: --- → 1
Priority: -- → P1
Pushed by chutten@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a5ee74afa9be Make note of deadlock potential in gv streaming telemetry r=janerik
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: