Closed Bug 613650 Opened 9 years ago Closed 4 years ago

[meta] GC mark phase topcrashes

Categories

(Core :: JavaScript Engine, defect)

defect
Not set

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.
Depends on: 585844
Some of them are blockers and some of them aren't? Does this mean we would punt on the blockers re: "give us altogether"?
(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.
Depends on: 615098
Depends on: 628105
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).
(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.
Depends on: 503650
No longer depends on: 503650
Assignee: general → nobody
Please do!
Flags: needinfo?(terrence)
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.