Our assertion macros could capture the JS stack

NEW
Unassigned

Status

()

Core
XPCOM
4 years ago
4 years ago

People

(Reporter: Yoric, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

At the moment, if a crash was caused by JS, we have no information in the Crash Report.

I believe it may be possible to capture the JS stack in some cases, namely if the crash takes place because of an assertion failure.

We would need a strategy to handle crashes inside the JS stack walker, of course.
Do you mean calling DumpJSStack() or something more sophisticated?
I mean calling DumpJSStack() or equivalent.
What Benjamin said on dev-platform!  ;-)  But FWIW I think for debug-only assertions, some of those concerns might not apply...
You need to log in before you can comment on or make changes to this bug.