1346849 - console.log sometimes doesn't show stack trace from Error

Status: RESOLVED WORKSFORME

(DevTools :: Console, defect)

Description

[Tom Tromey :tromey]

Attachment: Screenshot from 2017-03-13 17-43-48.png

This bug is a bit funny in that I couldn't reproduce it using
a simple test case, only by modifying the sources.

To reproduce:

1. edit devtools/client/webconsole/new-console-output/components/grip-message-body.js
   put this line at the top of function GripMessageBody:

  console.log(new Error("T"));

2. Rebuild and run the new browser

3. Open the browser console
4. Open the web console
5. In the web console, type the string constant "x"
   This will run the code changed in step 1

Here I expect to see the logged Error with it stack trace.
Instead I see:

Stack trace:
[object Object]

I'll attach a screenshot.

A simple test like this:

  function f() { console.log(new Error("T")); }
  function g() { f(); }

... typed into the console, then calling g(), does the right thing.

Comment 1

[Nicolas Chevobbe [:nchevobbe]]

Attachment: Screenshot at Jul 13 07-48-39.png

I couldn't reproduce the Bug following Comment 0 STR. I do see the stacktrace.
This might have been resolved by Bug 1362023.