Closed Bug 1395778 Opened 7 years ago Closed 7 years ago

Crash in pages_commit

Categories

(Core :: Memory Allocator, defect)

Unspecified
Windows 10
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 1229384
Tracking Status
firefox57 --- affected

People

(Reporter: marcia, Unassigned)

References

Details

(Keywords: crash)

This bug was filed from the Socorro interface and is report bp-5eec4421-0b39-4a74-9120-eaecc0170901. ============================================================= Seen while looking at crash stats: http://bit.ly/2emUlle. Crashes started using 20170831100258. 31 crashes/12 installs. Possible regression from Bug 1395063?
Flags: needinfo?(mh+mozilla)
As mentioned in the commit message in bug 1395063, it changed the crash signatures, so instead of having crashes in moz_abort that come from page_commit, you now have crashes in page_commit directly.
Flags: needinfo?(mh+mozilla)
See also bug 1395805. glandium, is this likely to be generic heap corruption?
Flags: needinfo?(mh+mozilla)
More like OOM. (VirtualAlloc failing)
Flags: needinfo?(mh+mozilla)
I'll file a bug to get something added to the Socorro prefix list so these different overcommit crashes don't end up in a single bucket, like they were before.
(In reply to Andrew McCreight [:mccr8] from comment #6) > I'll file a bug to get something added to the Socorro prefix list so these > different overcommit crashes don't end up in a single bucket, like they were > before. Well, I guess that doesn't make too much sense. I didn't realize the old signature also wasn't going very far on the prefix list. I'll just dupe this over to the old bug for this signature, and add the signature.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Crash Signature: [@ pages_commit]
You need to log in before you can comment on or make changes to this bug.