Closed Bug 1012691 Opened 8 years ago Closed 8 years ago

crash in NS_ABORT_OOM(unsigned int) | PL_DHashTableInit(PLDHashTable*, PLDHashTableOps const*, void*, unsigned int, unsigned int) | nsCycleCollector::BeginCollection(ccType, nsICycleCollectorListener*)

Categories

(Core :: XPCOM, defect)

30 Branch
x86
Windows NT
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: tracy, Unassigned)

Details

(Keywords: crash, topcrash-win)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-d60b8812-6da3-414f-986a-1a7f22140512.
=============================================================

Filling this a follow up to bug 1006181 to address this crash on Fx30 and Fx31

OOM Allocation Size: 262144
I don't understand what this bug is tracking. The big increase in this signature was because of the memory leak/usage from HTTP cache v2, which isn't on fx30/31. Otherwise this is just an OOM crash, which we don't typically file or track.
Flags: needinfo?(twalker)
(In reply to Benjamin Smedberg  [:bsmedberg] from comment #1)
> Otherwise this is just an OOM crash, which we don't typically file or track.

We want a bug on file about any signature in the higher ranks on any release. This is in the top 20 on Fx30, so that warrants having a bug to track it. If it's a dummy because this is generic OOM, so be it.

That said, I wonder if it's good that we require to allocate new memory to run CC, which should hopefully free up some memory.
Oh, and comment #2 answers the ni? - even more as I asked tracy to file a new bug instead of sticking Fx30 stuff into bug 1006181 which is about cache2, which does not apply to 30 (or 31).
Flags: needinfo?(twalker)
Is the total volume of OOM crashes worse in FF30 than in previous releases? If so, please file a bug on that specifically.

This bug is not actionable. I think I disagree with your policy of filing a bug for each OOM bug separately, instead of adding them to some meta-bug, but if you do, please mark it INCOMPLETE as you file it.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
(In reply to Benjamin Smedberg  [:bsmedberg] from comment #4)
> This bug is not actionable. I think I disagree with your policy of filing a
> bug for each OOM bug separately, instead of adding them to some meta-bug

I didn't say we need to have each one filed separately. We just want to have the signature be connected to some bug that actually has to do with what this is. I do not think we should resolve bugs that are valid crashes as INCOMPLETE even if they might not be actionable.
INCOMPLETE, so, not tracking.
Yeah, this will have morphed into one of the generic OOM signatures.
You need to log in before you can comment on or make changes to this bug.