Open
Bug 1611459
Opened 5 years ago
Updated 2 years ago
ErrorReport::populateUncaughtExceptionReportUTF8VA() can result in a null filename
Categories
(Core :: JavaScript Engine, task, P2)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: mccr8, Unassigned)
References
(Blocks 1 open bug)
Details
Quoting myself from bug 1611280: "ErrorReport::populateUncaughtExceptionReportUTF8VA() looks like it is another place that can result in a null filename. If I'm reading this correctly, it looks like this could happen if we end up in some kind of fallback exception creating code in ErrorReport::init(), when the top of the JS stack is self-hosted code. Maybe we could put a generic value as a file name in that case, or maybe we could just fail and hope something okay happens."
Reporter | ||
Comment 1•5 years ago
|
||
It also looks like a script source can have a null file name, for instance if there's an OOM when setting the file name on the script source. So it may be tricky to avoid that.
Updated•5 years ago
|
Priority: -- → P2
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•