1225760 - Crash in @dosprintf from XML parser error handler

Status: RESOLVED WORKSFORME

(Core :: General, defect)

Description

[Pascal Chevrel (relman team) -> :pascalc]

This is a crash reported by a friend via twitter:
https://twitter.com/pascal_martin/status/666887863087325184

I am in contact with him, this is on an intranet page and the page also uses javascript libraries (jquery, highcharts + custom code) that reload monitoring widgets on a page. So we don't yet know what causes it to crash Firefox after a while, we will probably have to triage that bug to the right component.


Here is the crash ID: bp-65d05573-32ac-40e0-8e15-93a0c2151118

A visible symptom was that the animated gif was freezing more and more often and for longer times over time. After a while, Firefox crashed. Tentatively putting that into Core:Imagelib

Comment 1

[Mike Hommey [:glandium]]

The crash report looks like it comes from a distro build. It would interesting to get a crash report from a mozilla.org build (or lack thereof, considering the code of the crash, it could be caused by hardening, which is enabled on Ubuntu, but not on mozilla.org builds)

Comment 2

[Josh Matthews [:jdm]]

The crash here is coming from the XML parser error handler, which is calling into nsTextFormatter and something is going awry. Images appear to be a red herring

Comment 3

[Boris Zbarsky [:bzbarsky]]

Needinfo for comment 1.

Comment 4

[Pascal Chevrel (relman team) -> :pascalc]

The needinfo should be on the other Pascal on the bug ;)

Pascal, do you think we could try to reproduce your crash with an official mozilla build instead of a distro one?

Comment 5

[contact]

Hi,

It is indeed a distro build, from Ubuntu.

I'll set up a VM with a mozilla.org build and point it to a local version of that intranet page (with the same gif, which is no longer visible on the real page ; and trying to get some live-like data in the other widgets) to see if I can reproduce the crash.

FYI: "the page" is a board displaying some live-data on a big TV-screen, so there is pretty much never any full-page refresh : only widgets being refreshed using some bits of Ajax.
The animated gif was in one of those widgets, which had not been updated for a few days (week-end).

On the live intranet with the real computer displaying it, it took approx. 4 days between the time the gif appeared on the page and the crash (and approx. 6 days between the last full-refresh of the page and the crash).

I'll come back to you when I have more data with a mozilla.org build.

Comment 6

[u279076]

More reports here:
https://crash-stats.mozilla.com/report/list?product=Firefox&signature=dosprintf

67% of the reports are with Linux but we have reports on Windows and OS X as well.
48% of the reports are with Firefox but we have reports on Thunderbird and Fennec as well.
25% of the reports are with Firefox 42 but we have reports going all the way back to Firefox 26.
100% of the Linux crashes come from Ubuntu's version, not ours nor any other distro's.

Based on the data I suspect this may be multiple issues under the same signature.

Comment 7

[Wayne Mery (:wsmwk)]

According to graph the crash is virtually gone after March 5
https://crash-stats.mozilla.com/signature/?signature=dosprintf&date=%3E%3D2018-02-13T02%3A05%3A14.000Z&date=%3C2018-08-13T04%3A05%3A14.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=install_time&_sort=-date&page=1#graphs 

WFM?

Comment 8

[Marissa (Reese) Wood]

I think we can close this one.