1920122 - webrtcIndicator.xhtml triggers a YSOD

Status: NEW

(Core :: XPCOM, defect)

Description

[Greg Tatum [:gregtatum]]

I was looking at Glean migration of the YSOD telemetry (yellow screen of death) and found something that looks like a bug that should be fixed.

chrome://browser/content/webrtcIndicator.xhtml is the top source of YSODs.

https://sql.telemetry.mozilla.org/queries/102383/source

chrome://browser/content/webrtcIndicator.xhtml:1:1 - XML_ERROR_NO_ELEMENTS

Comment 1

[Greg Tatum [:gregtatum]]

I'm wondering if a document is failing to load, as there are other pages with similar errors, at a lower frequency.

Comment 2

[Emma Zühlcke [:emz]]

Could this be a dupe of https://bugzilla.mozilla.org/show_bug.cgi?id=1639821?

Comment 3

[Greg Tatum [:gregtatum]]

Ah possibly! It may be just from older clients.

Comment 4

[Greg Tatum [:gregtatum]]

No, it's still around: https://sql.telemetry.mozilla.org/queries/102384/source

Comment 5

[Valentin Gosu [:valentin] {{ PTO 3 July - 3 August }}]

Looking at the call trace of where we record this probe I wonder if it would be useful to also capture the stream status in telemetry. Maybe nsParser::mInternalState too?
I'm assuming there are no onDataAvailables - and if so it would be useful to find out why.
I think we can pass that value into nsExpatDriver here

Comment 6

[Nika Layzell [:nika] (ni? for response)]

Is there any chance that this is the first xhtml document we try to load from the browser omnijar? It seems odd that this specific document would be the one seen to fail in these situations, as I would expect the rest of the browser to be unstable if the browser omnijar is missing/corrupted.