Chrome Constantly Freezes/Unresponsive to Input When Inspector Is Open












0














First of all, I have already tried disabling hardware acceleration, re-installing Chrome, even re-installing Mac OS Mojave. Non of these solved my issues.



After 5-10 minutes of using Chrome with the inspector window open, it becomes extremely buggy!



Hovering over items in the elements tab of the inspector window no longer highlights those items blue on the page. Clicking to modify an attribute on an element does allow me to edit it, but the typing cursor has disappeared and the ability to select text is gone, so I am typing/editing blind. The same thing happens when trying to edit a style in the right column under the styles tab, I can click to edit it but the typing cursor is missing, and I cannot select/highlight text.



In addition, when I am done editing a style, attribute, or text in the Elements window, you cannot close out of the style, parameter, or text - it just remains in the edit state. At this point trying to change to another element is difficult. I have to double click, or even triple click to go to another element, and it's not highlight the element blue on the page.



In the source tab, if I try to debug javascript, it brings Chrome to a crawl, and I cannot click the step over/step into buttons, it's very slow to respond, sometimes I have to double click, or triple click for it to respond to my click to step.



Also, when Chrome has become unresponsive like this, the ability to click and drag the handlebars on the responsive resizing window is missing, I cannot drag to resize the browser window (using the responsive handles).



Finally, during this buggy state in Chrome, the browser window will not accept text input anywhere, either on the address bar or on a webpage itself.



I can relieve the issue of the browser not accepting text input by closing the inspector, but after I re-open it the issues re-appear unless I restart Chrome. Sometimes I am having to restart Chrome every 10 minutes. This has been happening for about 3 months now.



Before then, I had none of these issue.










share|improve this question



























    0














    First of all, I have already tried disabling hardware acceleration, re-installing Chrome, even re-installing Mac OS Mojave. Non of these solved my issues.



    After 5-10 minutes of using Chrome with the inspector window open, it becomes extremely buggy!



    Hovering over items in the elements tab of the inspector window no longer highlights those items blue on the page. Clicking to modify an attribute on an element does allow me to edit it, but the typing cursor has disappeared and the ability to select text is gone, so I am typing/editing blind. The same thing happens when trying to edit a style in the right column under the styles tab, I can click to edit it but the typing cursor is missing, and I cannot select/highlight text.



    In addition, when I am done editing a style, attribute, or text in the Elements window, you cannot close out of the style, parameter, or text - it just remains in the edit state. At this point trying to change to another element is difficult. I have to double click, or even triple click to go to another element, and it's not highlight the element blue on the page.



    In the source tab, if I try to debug javascript, it brings Chrome to a crawl, and I cannot click the step over/step into buttons, it's very slow to respond, sometimes I have to double click, or triple click for it to respond to my click to step.



    Also, when Chrome has become unresponsive like this, the ability to click and drag the handlebars on the responsive resizing window is missing, I cannot drag to resize the browser window (using the responsive handles).



    Finally, during this buggy state in Chrome, the browser window will not accept text input anywhere, either on the address bar or on a webpage itself.



    I can relieve the issue of the browser not accepting text input by closing the inspector, but after I re-open it the issues re-appear unless I restart Chrome. Sometimes I am having to restart Chrome every 10 minutes. This has been happening for about 3 months now.



    Before then, I had none of these issue.










    share|improve this question

























      0












      0








      0







      First of all, I have already tried disabling hardware acceleration, re-installing Chrome, even re-installing Mac OS Mojave. Non of these solved my issues.



      After 5-10 minutes of using Chrome with the inspector window open, it becomes extremely buggy!



      Hovering over items in the elements tab of the inspector window no longer highlights those items blue on the page. Clicking to modify an attribute on an element does allow me to edit it, but the typing cursor has disappeared and the ability to select text is gone, so I am typing/editing blind. The same thing happens when trying to edit a style in the right column under the styles tab, I can click to edit it but the typing cursor is missing, and I cannot select/highlight text.



      In addition, when I am done editing a style, attribute, or text in the Elements window, you cannot close out of the style, parameter, or text - it just remains in the edit state. At this point trying to change to another element is difficult. I have to double click, or even triple click to go to another element, and it's not highlight the element blue on the page.



      In the source tab, if I try to debug javascript, it brings Chrome to a crawl, and I cannot click the step over/step into buttons, it's very slow to respond, sometimes I have to double click, or triple click for it to respond to my click to step.



      Also, when Chrome has become unresponsive like this, the ability to click and drag the handlebars on the responsive resizing window is missing, I cannot drag to resize the browser window (using the responsive handles).



      Finally, during this buggy state in Chrome, the browser window will not accept text input anywhere, either on the address bar or on a webpage itself.



      I can relieve the issue of the browser not accepting text input by closing the inspector, but after I re-open it the issues re-appear unless I restart Chrome. Sometimes I am having to restart Chrome every 10 minutes. This has been happening for about 3 months now.



      Before then, I had none of these issue.










      share|improve this question













      First of all, I have already tried disabling hardware acceleration, re-installing Chrome, even re-installing Mac OS Mojave. Non of these solved my issues.



      After 5-10 minutes of using Chrome with the inspector window open, it becomes extremely buggy!



      Hovering over items in the elements tab of the inspector window no longer highlights those items blue on the page. Clicking to modify an attribute on an element does allow me to edit it, but the typing cursor has disappeared and the ability to select text is gone, so I am typing/editing blind. The same thing happens when trying to edit a style in the right column under the styles tab, I can click to edit it but the typing cursor is missing, and I cannot select/highlight text.



      In addition, when I am done editing a style, attribute, or text in the Elements window, you cannot close out of the style, parameter, or text - it just remains in the edit state. At this point trying to change to another element is difficult. I have to double click, or even triple click to go to another element, and it's not highlight the element blue on the page.



      In the source tab, if I try to debug javascript, it brings Chrome to a crawl, and I cannot click the step over/step into buttons, it's very slow to respond, sometimes I have to double click, or triple click for it to respond to my click to step.



      Also, when Chrome has become unresponsive like this, the ability to click and drag the handlebars on the responsive resizing window is missing, I cannot drag to resize the browser window (using the responsive handles).



      Finally, during this buggy state in Chrome, the browser window will not accept text input anywhere, either on the address bar or on a webpage itself.



      I can relieve the issue of the browser not accepting text input by closing the inspector, but after I re-open it the issues re-appear unless I restart Chrome. Sometimes I am having to restart Chrome every 10 minutes. This has been happening for about 3 months now.



      Before then, I had none of these issue.







      google-chrome performance browser freeze google-chrome-devtools






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 10 '18 at 20:47









      Scott Taylor

      11




      11






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          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%2fsuperuser.com%2fquestions%2f1382432%2fchrome-constantly-freezes-unresponsive-to-input-when-inspector-is-open%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • 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.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • 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%2fsuperuser.com%2fquestions%2f1382432%2fchrome-constantly-freezes-unresponsive-to-input-when-inspector-is-open%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

          Plaza Victoria

          Puebla de Zaragoza

          Musa