Chrome too slow when debug minified javascript source
Reported by
elcondor...@gmail.com,
Sep 29 2016
|
|||||
Issue descriptionChrome Version : 53.0.2785.116 m (64-bit) What steps will reproduce the problem? Open the attached html file with Chrome and put a breakpoint in the indicated point. Reaload the page and when the execution stops, press F11 to step in. Chrome will freeze for to many time for to show the execution point within the minimized javascript file. What is the expected result? Chrome should show the execution point fast. What happens instead? Chrome freezing for many time to show the execution point in the minimized javascript file.
,
Feb 20 2017
Able to reproduce this issue on Win-10 and Ubuntu 14.04 using chrome reported version #56.0.2924.87 and latest canary #58.0.3017.0. This is a non-regression issue as it is observed from M40 old builds. For M30 and M35 builds upon opening the test.html file, the code was not visible in the sources tab of devtools in order to put the breakpoint. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Feb 21 2017
Our code editor doesn't viewport things horizontally. And blink is pretty slow rendering enourmously long lines. Joel, what can we do about this? This indeed kills devtools.
,
Jun 9 2017
,
Feb 24 2018
Any news about it?
,
Dec 14
Issue 891248 has been merged into this issue. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by elcondor...@gmail.com
, Feb 15 2017