DevTools: console.trace has expanded stack trace by default
Reported by
xixi...@gmail.com,
Jan 3 2017
|
|||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:50.0) Gecko/20100101 Firefox/50.0
Steps to reproduce the problem:
1. console.trace("something") in the console
2. trace is expanded
What is the expected behavior?
Trace is collapsed and can be expanded by clicking on the chevron in top left.
What went wrong?
Trace is expanded by default. In practice, since stack traces are usually long, this makes the console output unusable once you trace more than one time.
Did this work before? Yes This didn't happen at the end of November 2016.
Chrome version: 55.0.2883.95 Channel: stable
OS Version: OS X 10.12.1
Flash Version:
If this is the desired behavior, can we have a setting that toggles it, or a programmatic way to prevent it?
,
Jan 4 2017
Able to reproduce this issue on Windows-10, Ubuntu 14.04 and Mac OS 10.12 using chrome latest stable M55-55.0.2883.87. Good build: 55.0.2855.0 Bad Build: 55.0.2857.0 Using the per-revision bisect providing the bisect results, You are probably looking for a change made after 417804 (known good), but no later than 417805 (first known bad). CHANGE-LOG URL: --------------- https://chromium.googlesource.com/chromium/src/+log/681568d4e7a08a988d677d8ad76d79faf87e7d2e..e947ab6cc5cb2c09c98fe394a623d6c56047ad47 From the CL above, assigning the issue to the concern owner @dgozman : Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.
,
Jan 4 2017
This is not a security issue. Removing security labels.
,
Jan 4 2017
,
Jan 4 2017
Thanks for the report and bisect. We could either do a setting as you suggested, or perhaps keep traces collapsed when they are small (say <20? lines).
,
Jan 17 2017
Friendly ping to get an update on this.
,
Jan 18 2017
I discussed this with kozyatinskiy@, and we probably want to see the first N call frames and have a button "show more" to reveal all of them.
,
Apr 6 2017
> we probably want to see the first N call frames and have a button "show more" to reveal all of them. this SGTM.
,
Dec 20
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9fa9f218d69c1f528856b1bf5e41e804b7f3ae20 commit 9fa9f218d69c1f528856b1bf5e41e804b7f3ae20 Author: Erik Luo <luoe@chromium.org> Date: Thu Dec 20 00:51:03 2018 DevTools: trim long console traces by default Bug: 677929 Change-Id: Iffe67ce7e2512e75ea8063fcc0cbda782eed2d95 Reviewed-on: https://chromium-review.googlesource.com/c/1383118 Commit-Queue: Erik Luo <luoe@chromium.org> Reviewed-by: Joel Einbinder <einbinder@chromium.org> Cr-Commit-Position: refs/heads/master@{#618046} [modify] https://crrev.com/9fa9f218d69c1f528856b1bf5e41e804b7f3ae20/third_party/blink/renderer/devtools/front_end/components/JSPresentationUtils.js [add] https://crrev.com/9fa9f218d69c1f528856b1bf5e41e804b7f3ae20/third_party/blink/web_tests/http/tests/devtools/console/console-trim-long-traces-expected.txt [add] https://crrev.com/9fa9f218d69c1f528856b1bf5e41e804b7f3ae20/third_party/blink/web_tests/http/tests/devtools/console/console-trim-long-traces.js
,
Dec 20
,
Jan 14
This has come back for me.... 14/01/2019 on the latest chrome (71.0.3578.98)
,
Jan 14
c#11: the fix has landed in M73, (currently Dev channel), not yet in stable. I would expect it to reach stable in several weeks. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ajha@chromium.org
, Jan 4 2017