Closed Bug 513332 Opened 12 years ago Closed 12 years ago
Crash at [@arena
_run _reg _alloc ]
More to the point, it's topcrash #14 for Firefox 3.0.13. There are some reports for Firefox 3.5.2 but not enough to make the top hundred list. Could this be a bug in jemalloc? Or an OOM symptom? Or does it indicate that some other code blew up the heap?
This is very likely either due to a buffer overrun corrupting internal malloc data structures, or due to a double free.
Fun :( And I suppose we have no good way of knowing whether it's one such bug or many. The good news is it's mostly Firefox 3.0.x.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
Crash Signature: [@arena_run_reg_alloc ]
You need to log in before you can comment on or make changes to this bug.