Closed Bug 519771 Opened 15 years ago Closed 15 years ago

Crash [@memmove | nsTArray_base::ShiftData(unsigned int, unsigned int, unsigned int, unsigned int) ]


(Core :: General, defect)

1.9.1 Branch
Windows XP
Not set



Tracking Status
status1.9.1 --- wanted


(Reporter: cbook, Assigned: sicking)


(Keywords: crash)

Crash Data

filing from the topcrash stats:|%20nsTArray_base%3A%3AShiftData%28unsigned%20int%2C%20unsigned%20int%2C%20unsigned%20int%2C%20unsigned%20int%29

one comment mentioned "once I uploaded mozilla it says I don't have enough memory and then it stops. should I uninstall it because it has been nothing but problems." but not sure how to reproduce
Flags: blocking1.9.2?
this is something we need to have urls for ?
I'll take this
Assignee: nobody → jonas
There are different stacks involved in this crash. That's why I'm not sure if bug 507114 is really a dupe of this one. I filed bug 507114 on request of dbaron based on his comment on bug 494617 which also have a similar stack. I'm confused now.
Just crashed my SM2RC1 with this crash-report after two-times pressing "k" for ignore on mailnews
Once this signature is split up (bug 520678), will we just mark this bug as invalid?
Jonas, is this likely fixed by bug 494617?
Only partially. I think bug 507114 is a bigger contributor.

Also note that this bug will basically be split up into several once bug 520678 is fixed.
Closed: 15 years ago
Resolution: --- → INVALID
Judging from the comments, a some or all of these crashes may be out-of-memory crashes.
This is currently ranked #56 overall top crash.  when we split this up into many signatures will all the new signatures scatter to the wind and be much harder to identify as a collective group of semi-related out-of-memory crashes?   I wonder if there is a way to hold on to this collective information and maybe use this as a tracking bug.
That's what bug 493779 is for.  We're also splitting "operator new" crashes in bug 511758, btw, and for the same reason: not all of them are due to high memory use.
Flags: blocking1.9.2?
Crash Signature: [@memmove | nsTArray_base::ShiftData(unsigned int, unsigned int, unsigned int, unsigned int) ]
You need to log in before you can comment on or make changes to this bug.