Chrome dev tools crashing when debugging JS












10















Been googling around a bit for the last week or two and haven't come up with any leads.



I believe this started ever since the latest major chrome web browser update, from 68 to 69. (currently on version 69.0.3497.100 )



Basically, when I'm using the chrome dev tools and debugging some javascript, the browser crashes when I begin typing a variable name into the console. I'll get a character or two in and then bam, the whole thing crashes.



dev tools crash warning



I'll close the browser, reopen it and still crashes immediately when typing in the console. Sometimes there are a few hours in between episodes, but this has been a persistent issue for too long and is severely impacting my ability as a developer.



Any help would be greatly appreciated. Thanks.










share|improve this question




















  • 2





    not sure if that can be answered here, might be better suited on the chromium bugtracker

    – Jonas Wilms
    Sep 27 '18 at 18:06











  • I'll go poke around there, thanks

    – Josh Leslie
    Sep 27 '18 at 23:26






  • 1





    I've been hitting the same issue on Chrome 69. After doing some digging, I think this bug is related: bugs.chromium.org/p/chromium/issues/detail?id=729826

    – Joe Quigley
    Oct 10 '18 at 16:13











  • That does look related. I looked a bit for answers, but didn't find anything useful. I've been so busy with work I just switched to firefox's dev tools. They have their own issues, but at least it's not crashing dozens of times during my workday. Their HTML pane is a bit nicer too

    – Josh Leslie
    Oct 11 '18 at 19:07













  • I also have issues with Chrome 69 & DevTools "quitting" when stepping through code. Using React/Redux stack. Had no issues in Chrome 68. Tried uninstalling React/Redux developer extensions, but would still crash without them installed.

    – Phil Lucks
    Oct 15 '18 at 16:26


















10















Been googling around a bit for the last week or two and haven't come up with any leads.



I believe this started ever since the latest major chrome web browser update, from 68 to 69. (currently on version 69.0.3497.100 )



Basically, when I'm using the chrome dev tools and debugging some javascript, the browser crashes when I begin typing a variable name into the console. I'll get a character or two in and then bam, the whole thing crashes.



dev tools crash warning



I'll close the browser, reopen it and still crashes immediately when typing in the console. Sometimes there are a few hours in between episodes, but this has been a persistent issue for too long and is severely impacting my ability as a developer.



Any help would be greatly appreciated. Thanks.










share|improve this question




















  • 2





    not sure if that can be answered here, might be better suited on the chromium bugtracker

    – Jonas Wilms
    Sep 27 '18 at 18:06











  • I'll go poke around there, thanks

    – Josh Leslie
    Sep 27 '18 at 23:26






  • 1





    I've been hitting the same issue on Chrome 69. After doing some digging, I think this bug is related: bugs.chromium.org/p/chromium/issues/detail?id=729826

    – Joe Quigley
    Oct 10 '18 at 16:13











  • That does look related. I looked a bit for answers, but didn't find anything useful. I've been so busy with work I just switched to firefox's dev tools. They have their own issues, but at least it's not crashing dozens of times during my workday. Their HTML pane is a bit nicer too

    – Josh Leslie
    Oct 11 '18 at 19:07













  • I also have issues with Chrome 69 & DevTools "quitting" when stepping through code. Using React/Redux stack. Had no issues in Chrome 68. Tried uninstalling React/Redux developer extensions, but would still crash without them installed.

    – Phil Lucks
    Oct 15 '18 at 16:26
















10












10








10


2






Been googling around a bit for the last week or two and haven't come up with any leads.



I believe this started ever since the latest major chrome web browser update, from 68 to 69. (currently on version 69.0.3497.100 )



Basically, when I'm using the chrome dev tools and debugging some javascript, the browser crashes when I begin typing a variable name into the console. I'll get a character or two in and then bam, the whole thing crashes.



dev tools crash warning



I'll close the browser, reopen it and still crashes immediately when typing in the console. Sometimes there are a few hours in between episodes, but this has been a persistent issue for too long and is severely impacting my ability as a developer.



Any help would be greatly appreciated. Thanks.










share|improve this question
















Been googling around a bit for the last week or two and haven't come up with any leads.



I believe this started ever since the latest major chrome web browser update, from 68 to 69. (currently on version 69.0.3497.100 )



Basically, when I'm using the chrome dev tools and debugging some javascript, the browser crashes when I begin typing a variable name into the console. I'll get a character or two in and then bam, the whole thing crashes.



dev tools crash warning



I'll close the browser, reopen it and still crashes immediately when typing in the console. Sometimes there are a few hours in between episodes, but this has been a persistent issue for too long and is severely impacting my ability as a developer.



Any help would be greatly appreciated. Thanks.







javascript google-chrome google-chrome-devtools






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 20 '18 at 7:16









AmerllicA

1




1










asked Sep 27 '18 at 18:04









Josh LeslieJosh Leslie

585




585








  • 2





    not sure if that can be answered here, might be better suited on the chromium bugtracker

    – Jonas Wilms
    Sep 27 '18 at 18:06











  • I'll go poke around there, thanks

    – Josh Leslie
    Sep 27 '18 at 23:26






  • 1





    I've been hitting the same issue on Chrome 69. After doing some digging, I think this bug is related: bugs.chromium.org/p/chromium/issues/detail?id=729826

    – Joe Quigley
    Oct 10 '18 at 16:13











  • That does look related. I looked a bit for answers, but didn't find anything useful. I've been so busy with work I just switched to firefox's dev tools. They have their own issues, but at least it's not crashing dozens of times during my workday. Their HTML pane is a bit nicer too

    – Josh Leslie
    Oct 11 '18 at 19:07













  • I also have issues with Chrome 69 & DevTools "quitting" when stepping through code. Using React/Redux stack. Had no issues in Chrome 68. Tried uninstalling React/Redux developer extensions, but would still crash without them installed.

    – Phil Lucks
    Oct 15 '18 at 16:26
















  • 2





    not sure if that can be answered here, might be better suited on the chromium bugtracker

    – Jonas Wilms
    Sep 27 '18 at 18:06











  • I'll go poke around there, thanks

    – Josh Leslie
    Sep 27 '18 at 23:26






  • 1





    I've been hitting the same issue on Chrome 69. After doing some digging, I think this bug is related: bugs.chromium.org/p/chromium/issues/detail?id=729826

    – Joe Quigley
    Oct 10 '18 at 16:13











  • That does look related. I looked a bit for answers, but didn't find anything useful. I've been so busy with work I just switched to firefox's dev tools. They have their own issues, but at least it's not crashing dozens of times during my workday. Their HTML pane is a bit nicer too

    – Josh Leslie
    Oct 11 '18 at 19:07













  • I also have issues with Chrome 69 & DevTools "quitting" when stepping through code. Using React/Redux stack. Had no issues in Chrome 68. Tried uninstalling React/Redux developer extensions, but would still crash without them installed.

    – Phil Lucks
    Oct 15 '18 at 16:26










2




2





not sure if that can be answered here, might be better suited on the chromium bugtracker

– Jonas Wilms
Sep 27 '18 at 18:06





not sure if that can be answered here, might be better suited on the chromium bugtracker

– Jonas Wilms
Sep 27 '18 at 18:06













I'll go poke around there, thanks

– Josh Leslie
Sep 27 '18 at 23:26





I'll go poke around there, thanks

– Josh Leslie
Sep 27 '18 at 23:26




1




1





I've been hitting the same issue on Chrome 69. After doing some digging, I think this bug is related: bugs.chromium.org/p/chromium/issues/detail?id=729826

– Joe Quigley
Oct 10 '18 at 16:13





I've been hitting the same issue on Chrome 69. After doing some digging, I think this bug is related: bugs.chromium.org/p/chromium/issues/detail?id=729826

– Joe Quigley
Oct 10 '18 at 16:13













That does look related. I looked a bit for answers, but didn't find anything useful. I've been so busy with work I just switched to firefox's dev tools. They have their own issues, but at least it's not crashing dozens of times during my workday. Their HTML pane is a bit nicer too

– Josh Leslie
Oct 11 '18 at 19:07







That does look related. I looked a bit for answers, but didn't find anything useful. I've been so busy with work I just switched to firefox's dev tools. They have their own issues, but at least it's not crashing dozens of times during my workday. Their HTML pane is a bit nicer too

– Josh Leslie
Oct 11 '18 at 19:07















I also have issues with Chrome 69 & DevTools "quitting" when stepping through code. Using React/Redux stack. Had no issues in Chrome 68. Tried uninstalling React/Redux developer extensions, but would still crash without them installed.

– Phil Lucks
Oct 15 '18 at 16:26







I also have issues with Chrome 69 & DevTools "quitting" when stepping through code. Using React/Redux stack. Had no issues in Chrome 68. Tried uninstalling React/Redux developer extensions, but would still crash without them installed.

– Phil Lucks
Oct 15 '18 at 16:26














1 Answer
1






active

oldest

votes


















3





+25









As pointed out on this Reddit post: Google Chrome 69 Issues, that particular version was riddled with bugs. One website, quoting here from the same reddit thread, titled their article as "Atrocious performance - Google Chrome 69".



While this is not a solution, the easiest thing you can do is update to the latest version. (70.0.3538.77, at the time of writing.)






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52542757%2fchrome-dev-tools-crashing-when-debugging-js%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    3





    +25









    As pointed out on this Reddit post: Google Chrome 69 Issues, that particular version was riddled with bugs. One website, quoting here from the same reddit thread, titled their article as "Atrocious performance - Google Chrome 69".



    While this is not a solution, the easiest thing you can do is update to the latest version. (70.0.3538.77, at the time of writing.)






    share|improve this answer




























      3





      +25









      As pointed out on this Reddit post: Google Chrome 69 Issues, that particular version was riddled with bugs. One website, quoting here from the same reddit thread, titled their article as "Atrocious performance - Google Chrome 69".



      While this is not a solution, the easiest thing you can do is update to the latest version. (70.0.3538.77, at the time of writing.)






      share|improve this answer


























        3





        +25







        3





        +25



        3




        +25





        As pointed out on this Reddit post: Google Chrome 69 Issues, that particular version was riddled with bugs. One website, quoting here from the same reddit thread, titled their article as "Atrocious performance - Google Chrome 69".



        While this is not a solution, the easiest thing you can do is update to the latest version. (70.0.3538.77, at the time of writing.)






        share|improve this answer













        As pointed out on this Reddit post: Google Chrome 69 Issues, that particular version was riddled with bugs. One website, quoting here from the same reddit thread, titled their article as "Atrocious performance - Google Chrome 69".



        While this is not a solution, the easiest thing you can do is update to the latest version. (70.0.3538.77, at the time of writing.)







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 20 '18 at 16:16









        Abhishek SoniAbhishek Soni

        1,15911131




        1,15911131






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52542757%2fchrome-dev-tools-crashing-when-debugging-js%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

            SQL update select statement

            'app-layout' is not a known element: how to share Component with different Modules