1339365 - Crash in `anonymous namespace''::internal_GetHistogramByEnumId

Status: VERIFIED FIXED

Description

[[:philipp]]

This bug was filed from the Socorro interface and is 
report bp-57ab43b4-f014-4bfb-952e-325df2170212.
=============================================================
Crashing Thread (65)
Frame 	Module 	Signature 	Source
0 	xul.dll 	`anonymous namespace'::internal_GetHistogramByEnumId 	toolkit/components/telemetry/TelemetryHistogram.cpp:418
1 	xul.dll 	TelemetryHistogram::Accumulate(mozilla::Telemetry::ID, unsigned int) 	toolkit/components/telemetry/TelemetryHistogram.cpp:1901
2 	xul.dll 	mozilla::psm::`anonymous namespace'::AuthCertificate 	security/manager/ssl/SSLServerCertVerification.cpp:1288
3 	xul.dll 	mozilla::psm::`anonymous namespace'::SSLServerCertVerificationJob::Run 	security/manager/ssl/SSLServerCertVerification.cpp:1439
4 	xul.dll 	nsThreadPool::Run() 	xpcom/threads/nsThreadPool.cpp:225
5 	xul.dll 	nsThread::ProcessNextEvent(bool, bool*) 	xpcom/threads/nsThread.cpp:1067
6 	xul.dll 	NS_ProcessNextEvent(nsIThread*, bool) 	xpcom/glue/nsThreadUtils.cpp:311
7 	xul.dll 	mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*) 	ipc/glue/MessagePump.cpp:338
8 	xul.dll 	MessageLoop::RunHandler() 	ipc/chromium/src/base/message_loop.cc:225
9 	xul.dll 	MessageLoop::Run() 	ipc/chromium/src/base/message_loop.cc:205
10 	xul.dll 	nsThread::ThreadFunc(void*) 	xpcom/threads/nsThread.cpp:465
11 	nss3.dll 	_PR_NativeRunThread 	nsprpub/pr/src/threads/combined/pruthr.c:397
12 	nss3.dll 	pr_root 	nsprpub/pr/src/md/windows/w95thred.c:95
13 	ucrtbase.dll 	thread_start<unsigned int (__stdcall*)(void*)> 	
14 	kernel32.dll 	BaseThreadInitThunk 	
15 	ntdll.dll 	__RtlUserThreadStart 	
16 	ntdll.dll 	_RtlUserThreadStart

this crash was spiking up on 2017-02-12 for a day on 32bit versions of firefox 51.0.1 on windows. many of the user comments mentioned a site called 9anime.to in relation to this kind of crash.

https://mozilla.github.io/stab-crashes/supergraph.html?s=`anonymous+namespace%27%27%3A%3Ainternal_GetHistogramByEnumId

Comment 1

[Georg Fritzsche [:gfritzsche]]

The triggering bug here is probably bug 1339010, where in SSLServerCertVerification.cpp uninitialized variables are being used for histogram ids.

However, we should probably catch this path to protect from errors in other components.
The crash occurs here, so a simple (and cheap) bounds check on the histogram id should be sufficient:
https://hg.mozilla.org/releases/mozilla-release/annotate/327e081221b0/toolkit/components/telemetry/TelemetryHistogram.cpp#l418

Comment 2

[Georg Fritzsche [:gfritzsche]]

[Tracking Requested - why for this release]:
Crash bug. Triggered from security/manager/ssl/ code, but best protected against from Telemetry code.

Comment 3

[Georg Fritzsche [:gfritzsche]]

Attachment: Move Histogram ID validity checks to outer API

This moves the histogram id checks consistently to the public Histogram API. Chris, can you review? Nathan, do you have any concerns with this?

Comment 4

[Georg Fritzsche [:gfritzsche]]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=27cfca7e8a901cc9dd6ddc8365dc492150d7676e

Comment 5

[Chris H-C :chutten [on PTO. Back on July 30]]

Comment on attachment 8837268 [details] [diff] [review]
Move Histogram ID validity checks to outer API

Review of attachment 8837268 [details] [diff] [review]:
-----------------------------------------------------------------

I like the concept and the execution. The ipc refactor hasn't landed, has it? Because, if so, this won't apply.

Comment 6

[Georg Fritzsche [:gfritzsche]]

Comment on attachment 8837268 [details] [diff] [review]
Move Histogram ID validity checks to outer API

Actually this seems clear & simple enough, cancelling the additional feedback.

Comment 7

[Georg Fritzsche [:gfritzsche]]

(In reply to Chris H-C :chutten from comment #5)
> The ipc refactor hasn't landed, has
> it? Because, if so, this won't apply.

Right - the refactor will land with bug 1313326, which will land later.

Comment 8

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/d8e9eea586ed
Move Histogram ID validity checks to outer API. r=chutten

Comment 9

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/d8e9eea586ed

Comment 10

[Georg Fritzsche [:gfritzsche]]

Comment on attachment 8837268 [details] [diff] [review]
Move Histogram ID validity checks to outer API

Approval Request Comment
[Feature/Bug causing the regression]: Telemetry, recently triggered by security code bug.
[User impact if declined]: Risk of crash from out-of-bounds data access.
[Is this code covered by automated tests?]: Yes.
[Has the fix been verified in Nightly?]: Currently baking.
[Needs manual test from QE? If yes, steps to reproduce]: Per bug 1339010, comment 0, which should be confirmation steps for beta/aurora if bug 1339010 is not fixed there yet.
[List of other uplifts needed for the feature/fix]: n/a
[Is the change risky?]: Low-risk.
[Why is the change risky/not risky?]: This is a limited moving of code - an identifier validity check - to an outer API and skipping code if the check fails.
[String changes made/needed]: None.

Comment 11

[Gerry Chang [:gchang]]

Comment on attachment 8837268 [details] [diff] [review]
Move Histogram ID validity checks to outer API

Fix a crash. Aurora53+.

Comment 12

[Julien Cristau [:jcristau] (back on August 5)]

Comment on attachment 8837268 [details] [diff] [review]
Move Histogram ID validity checks to outer API

fix crash in telemetry code, beta52+

Comment 13

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/releases/mozilla-aurora/rev/50b11ab79661

Comment 14

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/releases/mozilla-beta/rev/b9a1b65ec610

Comment 15

[Andrei Vaida [:avaida]]

Flagging this for verification, instructions in Comment 10.

Comment 16

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/releases/mozilla-esr52/rev/b9a1b65ec610

Comment 17

[Bogdan Maris [:bogdan_maris], Release Desktop QA]

Was unable to reproduce the initial crash using steps from bug 1339010, comment 0 using old Nightly debug build from 2017-02-12, normal Nightly from the same date and Fx 51.0.1 on Windows 7 and 10 both x86. If we look at Socorro we can't see any crashes in the last few days in 52.

https://crash-stats.mozilla.com/signature/?product=Firefox&signature=%60anonymous%20namespace%27%27%3A%3Ainternal_GetHistogramByEnumId&date=%3E%3D2017-02-14T14%3A05%3A00.000Z&date=%3C2017-02-21T14%3A05%3A00.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_sort=-date&page=1#reports

Will this be enough to call this Fixed on 52?

Comment 18

[Georg Fritzsche [:gfritzsche]]

Thanks, i think crash-stats showing this as gone on 52 is sufficient.

Comment 19

[Bogdan Maris [:bogdan_maris], Release Desktop QA]

(In reply to Georg Fritzsche [:gfritzsche] from comment #18)
> Thanks, i think crash-stats showing this as gone on 52 is sufficient.

Thank you! Marking accordingly.

Comment 20

[Paul Silaghi, QA [:pauly]]

I see a few crashes newer than 2016-02-16:
https://crash-stats.mozilla.com/signature/?build_id=%3E20170216094131&signature=%60anonymous%20namespace%27%27%3A%3Ainternal_GetHistogramByEnumId&date=%3E%3D2017-02-22T14%3A37%3A10.000Z&date=%3C2017-03-08T14%3A37%3A10.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_sort=-date&page=1#reports
Thoughts?

Comment 21

[Georg Fritzsche [:gfritzsche]]

I only see like 3 for each channel & version in the last 14 days.
That seems like noise.

https://crash-stats.mozilla.com/signature/?build_id=%3E20170216094131&signature=%60anonymous%20namespace%27%27%3A%3Ainternal_GetHistogramByEnumId&date=%3E%3D2017-03-09T11%3A18%3A07.000Z&date=%3C2017-03-23T11%3A18%3A07.000Z

Comment 22

[Paul Silaghi, QA [:pauly]]

Verified fixed based on comment 21.