Closed
Bug 613650
Opened 14 years ago
Closed 9 years ago
[meta] GC mark phase topcrashes
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: dmandelin, Unassigned)
References
Details
There are several bugs on file for topcrashes that occur in the GC mark phase. I want to collect all of them together because:
- they may share underlying causes
- they may share diagnostic techniques
- we may want to decide to push ahead on them faster, or give up, all together.
Comment 1•14 years ago
|
||
Some of them are blockers and some of them aren't? Does this mean we would punt on the blockers re: "give us altogether"?
Reporter | ||
Comment 2•14 years ago
|
||
(In reply to comment #1)
> Some of them are blockers and some of them aren't? Does this mean we would punt
> on the blockers re: "give us altogether"?
I figured no one would be eager to start these fixing the blocker status wouldn't matter too much. :-) For the record, my intent is to try some diagnostics on bug 601457 after beta8 goes out, because I have the most understanding of that one and billm and I came up with some reasonable ideas for going forward on it. I will reconsider what to do with the others after that effort.
Comment 3•14 years ago
|
||
Are bug 601102 and bug 643746 also part of this group? They all have the two frames "js_TraceObject" and directly below a "js::gc::MarkChildren" in their stacks and they badly increased in 4.0 together with bug 615098 (interestingly since Monday and not just since Tuesday, which was release day).
Reporter | ||
Comment 4•14 years ago
|
||
(In reply to comment #3)
> Are bug 601102 and bug 643746 also part of this group? They all have the two
> frames "js_TraceObject" and directly below a "js::gc::MarkChildren" in their
> stacks and they badly increased in 4.0 together with bug 615098 (interestingly
> since Monday and not just since Tuesday, which was release day).
They are part of this group. We managed to solve them because they have a specific stack trace, which indicated (after a bunch of analysis) that they were related to exception stack trace capture.
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Comment 5•9 years ago
|
||
only bug 628105 is still open, but it's not in top 300. In fact it almost does not exist [1] so I'm going to close it.
https://crash-stats.mozilla.com/search/?signature=~js%3A%3Agc%3A%3AMarkString&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#crash-reports
Flags: needinfo?(terrence)
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•