794945 - crash in nsTimerImpl::Fire

Status: RESOLVED INCOMPLETE

(Core :: XPCOM, defect)

Description

[alex_mayorga]

This bug was filed from the Socorro interface and is 
report bp-a3ec42b7-380b-4b15-871a-823f92120927 .
============================================================= 

Filing after reviewing a user's crashes on 16.0 in SUMO[1].

1| https://support.mozilla.org/en-US/questions/938141

Comment 1

[Scoobidiver (away)]

It's a low volume crash: https://crash-stats.mozilla.com/report/list?signature=nsCOMPtr_base%3A%3Aassign_with_AddRef%28nsISupports*%29+|+nsTimerImpl%3A%3AFire%28%29

(In reply to alex_mayorga from comment #0)
> Filing after reviewing a user's crashes on 16.0 in SUMO[1].
See bug 770238 comment 10.

Comment 2

[Wayne Mery (:wsmwk)]

Alex, do you still crash with this signature? 

There are still crashes with this signature https://crash-stats.mozilla.com/report/list?signature=nsCOMPtr_base%3A%3Aassign_with_AddRef%28nsISupports*%29+|+nsTimerImpl%3A%3AFire%28%29&product=Firefox&query_type=contains&range_unit=weeks&process_type=any&hang_type=any&date=2014-10-06+02%3A00%3A00&range_value=1#tab-reports 

However, I doubt there is a common theme amongst them.

Comment 3

[alex_mayorga]

¡Hola Wayne!

It was not me crashing, but SUMO user https://support.mozilla.org/en-US/user/spikedsoda

Given the crash signature is still out there in the wild, this bug shall remain open, right?

Comment 4

[Wayne Mery (:wsmwk)]

(In reply to alex_mayorga from comment #3)
> ¡Hola Wayne!
> 
> It was not me crashing, but SUMO user
> https://support.mozilla.org/en-US/user/spikedsoda

Unfortunately he did not reply to the last question in https://support.mozilla.org/en-US/questions/938141   I've PMed him, perhaps he will respond.

> Given the crash signature is still out there in the wild, this bug shall
> remain open, right?

We could, but the signature is exceedingly rare and we have no steps to reproduce.  And iirc, it's easy for anyone to randomly crash in timer. And more than half the users I checked have multiple crash signatures, on or more of which will be more fruitful to persue than this bug.  For example one user has 4 crash sigs.

lookupName  
nsCOMPtr_base::assign_with_AddRef(nsISupports*) | nsTimerImpl::Fire()  
nsStyleContext::Release()  
mozilla::dom::FragmentOrElement::MarkNodeChildren(nsINode*)   
EnterBaseline  

so until useful information emerges I think we can say this is not actionable