--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/e1cf3152-593e-44b3-a3f4-c48de3be05c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
This looks like this bug: http://crbug.com/593679It would be great if you could provide your reproduction steps in the bug comments.Regards,Andrey
On Thu, Mar 17, 2016 at 10:48 AM roger reynolds <r...@rogerware.com> wrote:
I am also seeing this, just as of the latest update to version 49.0.2623.87
What is even worse is that chrome appears to remember the source files you had open, by site, so even after you kill the runaway chrome process, restart chrome, and even reboot your computer - you will immediately die once again if you open the developer tools for any page on that same site (that loads that same file anyway)For example, jquery.min.jsThis is a total catastrophe for chrome developer tools.Hoping a hot fix will be coming very soon, because it is completely unusable with this new "feature".--
On Wednesday, March 16, 2016 at 11:41:34 PM UTC-7, Filip Dupanović wrote:I've been working on a fairly big file with source maps and there haven't been any issues when accessing the sources. Usually, dev tools just hiccup for a few seconds and then the file is displayed. I'm sorry for being ignorant about the releases, but I've noticed some UI changes and now when accessing the source file dev tools freeze while loading the source maps.
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.