572501 - Examine 3.6.4 crashes in correlation with EMCheckCompatibility, installed extensions, and AMO updates on June 7

Status: RESOLVED FIXED

(Core :: General, defect)

Description

[Robert Sayre]

Looking over a particular crash signature that was new this week, I could see the jump on June 7. Every crash I examined had EMCheckCompatibility set to false and had a particular extension installed, identified only by uuid 972ce4c6-7e08-4474-a285-3208198ce6fd. It was listed as version 3.6.4... so maybe that's something we install by default? I dunno.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Modulo bugzilla totally mangling that "uuid ...." text, that extension id is the "extension id" of the default theme.

Comment 2

[Robert Sayre]

so uuid972ce4c6-7e08-4474-a285-3208198ce6fd

is the default theme ID. Do we set EMCheckCompatibility to false for all 3.6.4 installs?

Comment 3

[Johnathan Nightingale [:johnath]]

Just checked some 3.7a5 crashers and some 3.5.10 crashers, and they all have EMCheckCompatibility false as well - seems unlikely to me, unless that field is expressing the opposite thing (i.e. "Is EM check compatibility disabled?") Doesn't seem 3.6.4-specific...

Comment 4

[Dave Townsend [:mossop]]

Looks like Socorro is not collecting the EMCheckCompatibility flag correctly. I just did a crash of my nightly. Clicking through to the details in the breakpad prompt showed that it correctly had EMCheckCompatibility as true, yet the final crash report shows it as false: bp-dd16c567-9c5f-4aa4-b1ed-269b42100616

(In reply to comment #3)
> Just checked some 3.7a5 crashers and some 3.5.10 crashers, and they all have
> EMCheckCompatibility false as well

Pretty unlikely yes, we don't include the EMCheckCompatibility flag in 3.5 builds.

Comment 5

[Laura Thomson :laura]

Status please?

Comment 6

[Laura Thomson :laura]

Nothing else to do here, issue was resolved.