webpack dev server leading to freezing of the system












0














I was getting errors on using npm start in my react application. which goes like this
ENOSPC system limit for file watcher reached

I updated my npm and node versions but still i was getting this problem. After a little research i got to know that there is something known as inotify which watches different files and i need to increase its file watching limit. I used this code
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
in my terminal to increase the file watcher limit. After this i was succesfully able to do npm start and got my project running in localhost:3000, But this slowed my system incredibly, and it freezed every now and then. I highly suspect this is due to increasing number of file watchers. Is it the case if yes what should i do now??









share







New contributor




vaibnak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0














    I was getting errors on using npm start in my react application. which goes like this
    ENOSPC system limit for file watcher reached

    I updated my npm and node versions but still i was getting this problem. After a little research i got to know that there is something known as inotify which watches different files and i need to increase its file watching limit. I used this code
    echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
    in my terminal to increase the file watcher limit. After this i was succesfully able to do npm start and got my project running in localhost:3000, But this slowed my system incredibly, and it freezed every now and then. I highly suspect this is due to increasing number of file watchers. Is it the case if yes what should i do now??









    share







    New contributor




    vaibnak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0







      I was getting errors on using npm start in my react application. which goes like this
      ENOSPC system limit for file watcher reached

      I updated my npm and node versions but still i was getting this problem. After a little research i got to know that there is something known as inotify which watches different files and i need to increase its file watching limit. I used this code
      echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
      in my terminal to increase the file watcher limit. After this i was succesfully able to do npm start and got my project running in localhost:3000, But this slowed my system incredibly, and it freezed every now and then. I highly suspect this is due to increasing number of file watchers. Is it the case if yes what should i do now??









      share







      New contributor




      vaibnak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      I was getting errors on using npm start in my react application. which goes like this
      ENOSPC system limit for file watcher reached

      I updated my npm and node versions but still i was getting this problem. After a little research i got to know that there is something known as inotify which watches different files and i need to increase its file watching limit. I used this code
      echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
      in my terminal to increase the file watcher limit. After this i was succesfully able to do npm start and got my project running in localhost:3000, But this slowed my system incredibly, and it freezed every now and then. I highly suspect this is due to increasing number of file watchers. Is it the case if yes what should i do now??







      inotify





      share







      New contributor




      vaibnak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.










      share







      New contributor




      vaibnak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      share



      share






      New contributor




      vaibnak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 3 mins ago









      vaibnakvaibnak

      11




      11




      New contributor




      vaibnak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      vaibnak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      vaibnak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          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: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          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
          });


          }
          });






          vaibnak is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493621%2fwebpack-dev-server-leading-to-freezing-of-the-system%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








          vaibnak is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          vaibnak is a new contributor. Be nice, and check out our Code of Conduct.













          vaibnak is a new contributor. Be nice, and check out our Code of Conduct.












          vaibnak is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • 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%2funix.stackexchange.com%2fquestions%2f493621%2fwebpack-dev-server-leading-to-freezing-of-the-system%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

          CARDNET

          Boot-repair Failure: Unable to locate package grub-common:i386

          濃尾地震