Closed Bug 964351 Opened 10 years ago Closed 4 years ago

Spike in Aurora 28.0a2 as of 2014-01-26 with TppTimerpExecuteCallback

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Version:
28 Branch
Platform:
x86
Windows NT
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox26 --- unaffected
firefox27 --- unaffected
firefox28 --- affected
firefox29 --- unaffected
firefox48 --- affected
firefox49 --- affected
firefox-esr45 --- affected

People

(Reporter: u279076, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-4a0bc901-1fdb-4654-9954-c61dc2140127.
=============================================================
0 		@0x65fa2140 	
1 	ntdll.dll 	TppTimerpExecuteCallback 	
2 	ntdll.dll 	ntdll.dll@0x1f6c0 	
3 	kernel32.dll 	BaseThreadInitThunk 	
4 	ntdll.dll 	__RtlUserThreadStart 	
5 	ntdll.dll 	_RtlUserThreadStart 	

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

Current overall ranking:
 * Firefox 29: #143 @ 0.07% (-0.03%)
 * Firefox 28: #25 @ 0.49% (+0.14%)
 * Firefox 27: N/A (volume too low for topcrash reports)
 * Firefox 26: N/A (volume too low for topcrash reports)

Pushlog:
http://hg.mozilla.org/releases/mozilla-aurora/pushloghtml?fromchange=4b8d14a78596&tochange=c40099a42c1f
=============================================================

This signature has spiked on Aurora 28.0a2 starting on 2014-01-26 with 408 crashes per 1MM ADU (it's been in the 20-78 range over the previous week). It's not at a volume that we'd traditionally give topcrash designation to but it is a startup crash and the spike on Aurora seems suspect. Unfortunately I do not see any useful URLs, correlations, or comments.
KaiRo, do the top crash rankings count duplicate reports? There is one Aurora user who sent about 30 duplicates. This might not actually be a true spike...
Flags: needinfo?(kairo)
(In reply to David Major [:dmajor] from comment #1)
> KaiRo, do the top crash rankings count duplicate reports? There is one
> Aurora user who sent about 30 duplicates. This might not actually be a true
> spike...

Yes, we do not exclude duplicates in any reports as we don't completely trust the mechanism that marks them as dupes at this point. The long-term plan is to detect *real* dupes in a different way and exclude them, and then remove this dupe-marking completely.
Flags: needinfo?(kairo)
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #2)
Ok, thanks. Sounds like we shouldn't worry too much about this one.
not tracking as per comment 3
tracking-firefox28: ? → ---
The issue in Firefox 47 is bug 1270686.  Let's keep this bug about whatever the older issue was.
Crash volume for signature 'TppTimerpExecuteCallback':
 - nightly (version 51): 0 crashes from 2016-08-01.
 - aurora  (version 50): 0 crashes from 2016-08-01.
 - beta    (version 49): 75 crashes from 2016-08-02.
 - release (version 48): 18 crashes from 2016-07-25.
 - esr     (version 45): 6 crashes from 2016-05-02.

Crash volume on the last weeks (Week N is from 08-22 to 08-28):
            W. N-1  W. N-2  W. N-3
 - nightly       0       0       0
 - aurora        0       0       0
 - beta         22      29      13
 - release       5       4       3
 - esr           1       1       0

Affected platform: Windows

Crash rank on the last 7 days:
           Browser   Content     Plugin
 - nightly
 - aurora
 - beta    #910      #1841
 - release #1989
 - esr
status-firefox48: --- → affected
status-firefox49: --- → affected
status-firefox-esr45: --- → affected

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.