Open Bug 1292172 Opened 8 years ago Updated 1 month ago

new Proxy(new Error, ...) never contains stacktrace

Categories

(Core :: JavaScript Engine, defect, P3)

Product:
Core
Component:
JavaScript Engine
Version:
47 Branch
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: michalwadas, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: triage-deferred) 

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0
Build ID: 20160604131506

Steps to reproduce:

try { 
   throw new Error;
} catch(e) {
    console.log(e.stack)
}
try {
    throw new Proxy(new Error, {}); 
} catch(e) {
    console.log(e.stack)
}

Related Chrome issue: https://bugs.chromium.org/p/chromium/issues/detail?id=634340


Actual results:

"@debugger eval code:2:10"
""


Expected results:

"@debugger eval code:2:10"
""@debugger eval code:7:10"
Component: Untriaged → JavaScript Engine
Product: Firefox → Core
Keywords: triage-deferred
Priority: -- → P3

Still happens on Firefox 94.

Severity: normal → S3

Still broken in Chrome too; needs some investigation to see if this is actually working as expected (by spec let's say) or not.

Blocks: sm-runtime
You need to log in before you can comment on or make changes to this bug.