Closed Bug 1961851 Opened 1 year ago Closed 1 year ago

Improve error collection in User Characteristics Data

Categories

(Core :: Privacy: Anti-Tracking, enhancement)

enhancement

Tracking

()

RESOLVED FIXED
139 Branch
Tracking Status
firefox139 --- fixed

People

(Reporter: tjr, Assigned: fklc)

References

(Blocks 1 open bug)

Details

Attachments

(4 external files)

Looking at the errors we see in telemetry, can we make the following improvements?

try {
  const ctx = canvas.getContext("2d");
} except {
  raise "Error blah blah type: canvas.tagName"
}
  • About 25% of submissions have a populateWindowTimeout but after staring at it for a while I couldn't figure out a way to split the screen data from the pointer data (which is what I think is causing the vast majority of timeouts) in a way that seemed safe and wouldn't require e bunch of testing, so probably not worth it.
Assignee: nobody → fkilic

I have no idea why this would happen.

Pushed by fkilic@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/37d95cfb4773 Collect both rv and additional context. r=tjr https://hg.mozilla.org/integration/autoland/rev/d4a2ed977cd6 Check canvas element has getContext function. r=tjr https://hg.mozilla.org/integration/autoland/rev/a73c3c086a31 Split window info collection. r=tjr https://hg.mozilla.org/integration/autoland/rev/05f96912b032 Increment version. r=tjr

Sorry about it. Didn't get the same error on osx for some reason. I'll fix it thanks!

Flags: needinfo?(fkilic)
Pushed by fkilic@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/92ed5df0dc5a Collect both rv and additional context. r=tjr https://hg.mozilla.org/integration/autoland/rev/06ce78a4c865 Check canvas element has getContext function. r=tjr https://hg.mozilla.org/integration/autoland/rev/0e12d51fac94 Split window info collection. r=tjr https://hg.mozilla.org/integration/autoland/rev/9cfbff059e5b Increment version. r=tjr

We decided not to go forward with it but it looks like (i could be wrong) when we make a call from C++ to JS, if it throws an error, we store it here which can be later brought back from the js context's pending error like so.

So, if we ever want to get more detailed error details for CreateContentPage, then we can try using this method. (related convo on matrix 1, 2)

QA Whiteboard: [qa-triage-done-c140/b139]
Blocks: 1961809
Blocks: fpdata
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: