Closed Bug 1690444 Opened 4 years ago Closed 4 years ago

Add zero_byte_length Telemetry for JavaScript loads

Categories

(Core :: JavaScript Engine, task, P3)

task

Tracking

()

RESOLVED DUPLICATE of bug 1693146

People

(Reporter: zbraniecki, Assigned: kershaw)

References

(Blocks 1 open bug)

Details

As part of the crusade against Yellow Screen of Death, we would like to get telemetry probe for events of zero_byte_length loads of UI JS files to validate the hypothesis that zero_byte_length loads are the same class of problems as the YSOD events we observe in XUL.

This probe is particularly important because YSOD probe only shows XUL/XHTML/XML errors and indirectly indicates that DTD files are also affected.
But if JS file are also affected, then YSOD probe will not show it, while the UI will be completely broken.

The probe should report an event whenever there's a zero byte source string sent to JS parser for the chrome:// or resource:// URL and have the following event signature:

type: event
category: zero_byte_load
descriptuon: >-
  Collection of zero_byte_load events as part of the Yellow Screen of Death analysis.
  Theoretically, there should be no zero-byte-length loads, so every load of that type
  indicates an error, likely breaking user experience.
method: load
objects:
  - "ftl"
  - "dtd"
  - "properties"
  - "js"
  - "xml"
  - "html"
products: ["firefox"]
release_channel_collection: opt-out
value: URL
extra_key:
 - sync: bool

Each object will have its own bug. This one is for "js" event.

Assignee: nobody → kershaw
Blocks: 1675823
Severity: -- → N/A
Priority: -- → P3
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.