Issue metadata
Sign in to add a comment
|
Developer Tools crashes on sources search.
Reported by
jasondca...@gmail.com,
Mar 23 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. Open developer tools. 2. Use the keyboard short cut to open up the 'search/find' dialog. 3. Search for a term. What is the expected behavior? The developer tools script window should take you to the first found term and allow you to advance to the next term. What went wrong? Developer tools crashes. Did this work before? Yes Previous to 65.0.3325.181 Chrome version: 65.0.3325.181 Channel: stable OS Version: OS X 10.11.6 Flash Version: I believe I got the automatic update from Google to ver 65.0.3325.181. That is when I started having problems. My JS code is about 100K lines with Webpack/Babel/React. I've been working on my project for about a year and half. This has never been an issue before.
,
Mar 26 2018
,
Mar 26 2018
Unable to reproduce this issue on reported version 65.0.3325.181 using Mac 10.12.6 and Mac 10.13.3 with steps mentioned in comment#0. 1. Launched chrome, navigated to https://bugs.chromium.org/p/chromium/issues/detail?id=825399 and opened devtools sources section. 2. Hit Cmd+f, searched for word and didn't observe any crash. 3. Also checked with https://www.ucsf.edu/news/latest/patient-care URL. @Reporter: Please take a look at the video and let us know if we miss anything. Also please let us know if this happens only on particular site or seen on other sites as well. Also please attach a crash id from chrome://crashes. This would help in further debugging of the issue. Thanks!
,
Mar 26 2018
This may have something to do with the size of the JS being run. I can see from the video that it seems to work fine. If I wait (about 40 secs.) the "find" eventually resolves. The browser does not crash. Only the developer tools freezes. This is an issue for me, but it may only be me and transitory. I'll run a few more test this week and see if anything else about this issue pops up.
,
Mar 26 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 27 2018
Tested the issue with 3 MB size file and is not reproducible on Mac 10.13.3 and 10.12.6. Attaching it for reference. As per comment#4, waiting for reporters results. Hence adding Needs-Feedback label. Thanks!
,
Mar 30 2018
,
Apr 4 2018
Today I built a 5.5MB JS file using babel and webpack. I set up my test using the same build process I used in the initial bug report. I was not able to reproduce the issue. I also, separately, completely reinstalled Chrome. This did not fix my issue either. A clean JS build with +100K lines has no issue. It seems that there is something specific in my project that the Chrome Debugger has a problem with. I will continue to analyze this situation (I don't have any choice since Chrome is an important part of my development) but I can't say that it's a Chrome specific issue. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by jasondca...@gmail.com
, Mar 23 2018857 KB
857 KB View Download