Why running Facebook on Google Chrome uses so much memory?












2















When I log into Facebook on Google Chrome, my machine heats up, exhaust fans begin to run at super high speed and these are some technical results-
enter image description here



Running a single website, facebook specifically (no other webpage creates this problem), is requiring consistently 80% CPU and around 2.6 GB of RAM. Sometimes CPU usage rises upto even 95%.



Why is this happening?Why is a light job like running a web page (specifically Facebook) creating this issue?










share|improve this question


















  • 1





    It would be helpful to see what processes are actually running.

    – SiXandSeven8ths
    Feb 9 '18 at 20:56











  • I recently had the Chrome browser eat up my CPU but it was the Chrome software_reporter_tool.exe it had nothing to do with what page was viewing. You have to see what is running like suggested above.

    – Musselman
    Feb 10 '18 at 2:12











  • superuser.com/questions/1293083/…

    – magicandre1981
    Feb 10 '18 at 7:28
















2















When I log into Facebook on Google Chrome, my machine heats up, exhaust fans begin to run at super high speed and these are some technical results-
enter image description here



Running a single website, facebook specifically (no other webpage creates this problem), is requiring consistently 80% CPU and around 2.6 GB of RAM. Sometimes CPU usage rises upto even 95%.



Why is this happening?Why is a light job like running a web page (specifically Facebook) creating this issue?










share|improve this question


















  • 1





    It would be helpful to see what processes are actually running.

    – SiXandSeven8ths
    Feb 9 '18 at 20:56











  • I recently had the Chrome browser eat up my CPU but it was the Chrome software_reporter_tool.exe it had nothing to do with what page was viewing. You have to see what is running like suggested above.

    – Musselman
    Feb 10 '18 at 2:12











  • superuser.com/questions/1293083/…

    – magicandre1981
    Feb 10 '18 at 7:28














2












2








2








When I log into Facebook on Google Chrome, my machine heats up, exhaust fans begin to run at super high speed and these are some technical results-
enter image description here



Running a single website, facebook specifically (no other webpage creates this problem), is requiring consistently 80% CPU and around 2.6 GB of RAM. Sometimes CPU usage rises upto even 95%.



Why is this happening?Why is a light job like running a web page (specifically Facebook) creating this issue?










share|improve this question














When I log into Facebook on Google Chrome, my machine heats up, exhaust fans begin to run at super high speed and these are some technical results-
enter image description here



Running a single website, facebook specifically (no other webpage creates this problem), is requiring consistently 80% CPU and around 2.6 GB of RAM. Sometimes CPU usage rises upto even 95%.



Why is this happening?Why is a light job like running a web page (specifically Facebook) creating this issue?







google-chrome memory facebook






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 9 '18 at 18:30









tatantatan

12217




12217








  • 1





    It would be helpful to see what processes are actually running.

    – SiXandSeven8ths
    Feb 9 '18 at 20:56











  • I recently had the Chrome browser eat up my CPU but it was the Chrome software_reporter_tool.exe it had nothing to do with what page was viewing. You have to see what is running like suggested above.

    – Musselman
    Feb 10 '18 at 2:12











  • superuser.com/questions/1293083/…

    – magicandre1981
    Feb 10 '18 at 7:28














  • 1





    It would be helpful to see what processes are actually running.

    – SiXandSeven8ths
    Feb 9 '18 at 20:56











  • I recently had the Chrome browser eat up my CPU but it was the Chrome software_reporter_tool.exe it had nothing to do with what page was viewing. You have to see what is running like suggested above.

    – Musselman
    Feb 10 '18 at 2:12











  • superuser.com/questions/1293083/…

    – magicandre1981
    Feb 10 '18 at 7:28








1




1





It would be helpful to see what processes are actually running.

– SiXandSeven8ths
Feb 9 '18 at 20:56





It would be helpful to see what processes are actually running.

– SiXandSeven8ths
Feb 9 '18 at 20:56













I recently had the Chrome browser eat up my CPU but it was the Chrome software_reporter_tool.exe it had nothing to do with what page was viewing. You have to see what is running like suggested above.

– Musselman
Feb 10 '18 at 2:12





I recently had the Chrome browser eat up my CPU but it was the Chrome software_reporter_tool.exe it had nothing to do with what page was viewing. You have to see what is running like suggested above.

– Musselman
Feb 10 '18 at 2:12













superuser.com/questions/1293083/…

– magicandre1981
Feb 10 '18 at 7:28





superuser.com/questions/1293083/…

– magicandre1981
Feb 10 '18 at 7:28










3 Answers
3






active

oldest

votes


















0














Running a Facebook is obviously not a "light job".



Webpages serve a function for both the page viewer AND the page owner.



You require the page to be rendered, content from them to be cached, many requests to many other sites to processed to show the affiliate content, and videos to be ready and or playing, among other things.



They (the site owner) require fetching and displaying advertisements, analytics to be performed, and probably a plethora of unbenounced to us functions. These are things that most of us don't pay any real attention to on the front end but can consume a considerable amount of resources for no "perceived" benefit.



Point is the are many things independently happening to provide you with "the experience" and added up it requires alot of CPU and Memory rescources.






share|improve this answer



















  • 1





    That doesn't at all answer why OP is having issues with Facebook. I've never encountered such a thing, so this isn't just something as simple as "web pages uses resources."

    – SiXandSeven8ths
    Feb 9 '18 at 20:56



















0














Complementing what Damon said about the reasons for heavy loading due to advertisements and tracking, actualy i'm using some 'tricks' to minimize the problem with Facebook and other heavy sites.






  • AdGuard extension: Blocks all types of ads on all web pages, even on Facebook


  • AdBlock has many adBlockKillers, but does the same






  • Open Google Chrome on incognito mode using Ctrl + Shift + N keys


  • Incognito mode not save the history, but for me, in the most part of the time it's unnecessary.





If you want use both (I recommend) you need enable AdGuard in Incognito Mode:




  1. On Chrome open Menu ( three lines on the right side)

  2. Go to More tools and then Extensions

  3. To turn the extension on, check the box. To turn off an extension, uncheck the enabled box.






share|improve this answer































    0














    I've seen the same sort of issue on my pc with Chrome & Facebook. Almost never see the problem with any other page. I operate with a dozen or so tabs always open, multitasking. I find that this even happens with a freshly-loaded Facebook page, left idle for a long period of time (like overnight, after I've gone to sleep).



    I've used "Process Explorer", a replacement for Task Manager (actually available from Microsoft) for years. Its advantage is...instead of giving just one listing for each program...you get individual listings for each process. This means, for instance, you can have a dozen (or more) for Chrome. It also allows you to "kill" individual processes.



    enter image description here



    My workaround (not really a solution) is to find the process in ProcessExplorer using the largest amount of memory (I sort the processes by amount of memory being used)...and kill it. This "kills" the facebook page (gives you a blank white "page died" window in that tab) without killing Chrome entirely, and releases the massive amount of memory FB had locked down...letting you reload FB. As you can see in this pic, FB is already using 700+megs...and I've had it open less than 30 minutes. If I leave it alone long enough, that number will climb 'til it's using every bit of available memory. I typically have to kill FB every 2-3 hours.



    UPDATE: Here's what it looks like after I left a freshly loaded instance of Facebook open and untouched over the weekend (3 days). While it's like that, pages are sluggish as heck to load, anything & everything on the computer is dog-slow. Killing that process that's taking up 2.5gb of memory...instantly brings everything back to life.
    enter image description here






    share|improve this answer

























      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%2f1293546%2fwhy-running-facebook-on-google-chrome-uses-so-much-memory%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      Running a Facebook is obviously not a "light job".



      Webpages serve a function for both the page viewer AND the page owner.



      You require the page to be rendered, content from them to be cached, many requests to many other sites to processed to show the affiliate content, and videos to be ready and or playing, among other things.



      They (the site owner) require fetching and displaying advertisements, analytics to be performed, and probably a plethora of unbenounced to us functions. These are things that most of us don't pay any real attention to on the front end but can consume a considerable amount of resources for no "perceived" benefit.



      Point is the are many things independently happening to provide you with "the experience" and added up it requires alot of CPU and Memory rescources.






      share|improve this answer



















      • 1





        That doesn't at all answer why OP is having issues with Facebook. I've never encountered such a thing, so this isn't just something as simple as "web pages uses resources."

        – SiXandSeven8ths
        Feb 9 '18 at 20:56
















      0














      Running a Facebook is obviously not a "light job".



      Webpages serve a function for both the page viewer AND the page owner.



      You require the page to be rendered, content from them to be cached, many requests to many other sites to processed to show the affiliate content, and videos to be ready and or playing, among other things.



      They (the site owner) require fetching and displaying advertisements, analytics to be performed, and probably a plethora of unbenounced to us functions. These are things that most of us don't pay any real attention to on the front end but can consume a considerable amount of resources for no "perceived" benefit.



      Point is the are many things independently happening to provide you with "the experience" and added up it requires alot of CPU and Memory rescources.






      share|improve this answer



















      • 1





        That doesn't at all answer why OP is having issues with Facebook. I've never encountered such a thing, so this isn't just something as simple as "web pages uses resources."

        – SiXandSeven8ths
        Feb 9 '18 at 20:56














      0












      0








      0







      Running a Facebook is obviously not a "light job".



      Webpages serve a function for both the page viewer AND the page owner.



      You require the page to be rendered, content from them to be cached, many requests to many other sites to processed to show the affiliate content, and videos to be ready and or playing, among other things.



      They (the site owner) require fetching and displaying advertisements, analytics to be performed, and probably a plethora of unbenounced to us functions. These are things that most of us don't pay any real attention to on the front end but can consume a considerable amount of resources for no "perceived" benefit.



      Point is the are many things independently happening to provide you with "the experience" and added up it requires alot of CPU and Memory rescources.






      share|improve this answer













      Running a Facebook is obviously not a "light job".



      Webpages serve a function for both the page viewer AND the page owner.



      You require the page to be rendered, content from them to be cached, many requests to many other sites to processed to show the affiliate content, and videos to be ready and or playing, among other things.



      They (the site owner) require fetching and displaying advertisements, analytics to be performed, and probably a plethora of unbenounced to us functions. These are things that most of us don't pay any real attention to on the front end but can consume a considerable amount of resources for no "perceived" benefit.



      Point is the are many things independently happening to provide you with "the experience" and added up it requires alot of CPU and Memory rescources.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Feb 9 '18 at 18:45









      DamonDamon

      1,67111023




      1,67111023








      • 1





        That doesn't at all answer why OP is having issues with Facebook. I've never encountered such a thing, so this isn't just something as simple as "web pages uses resources."

        – SiXandSeven8ths
        Feb 9 '18 at 20:56














      • 1





        That doesn't at all answer why OP is having issues with Facebook. I've never encountered such a thing, so this isn't just something as simple as "web pages uses resources."

        – SiXandSeven8ths
        Feb 9 '18 at 20:56








      1




      1





      That doesn't at all answer why OP is having issues with Facebook. I've never encountered such a thing, so this isn't just something as simple as "web pages uses resources."

      – SiXandSeven8ths
      Feb 9 '18 at 20:56





      That doesn't at all answer why OP is having issues with Facebook. I've never encountered such a thing, so this isn't just something as simple as "web pages uses resources."

      – SiXandSeven8ths
      Feb 9 '18 at 20:56













      0














      Complementing what Damon said about the reasons for heavy loading due to advertisements and tracking, actualy i'm using some 'tricks' to minimize the problem with Facebook and other heavy sites.






      • AdGuard extension: Blocks all types of ads on all web pages, even on Facebook


      • AdBlock has many adBlockKillers, but does the same






      • Open Google Chrome on incognito mode using Ctrl + Shift + N keys


      • Incognito mode not save the history, but for me, in the most part of the time it's unnecessary.





      If you want use both (I recommend) you need enable AdGuard in Incognito Mode:




      1. On Chrome open Menu ( three lines on the right side)

      2. Go to More tools and then Extensions

      3. To turn the extension on, check the box. To turn off an extension, uncheck the enabled box.






      share|improve this answer




























        0














        Complementing what Damon said about the reasons for heavy loading due to advertisements and tracking, actualy i'm using some 'tricks' to minimize the problem with Facebook and other heavy sites.






        • AdGuard extension: Blocks all types of ads on all web pages, even on Facebook


        • AdBlock has many adBlockKillers, but does the same






        • Open Google Chrome on incognito mode using Ctrl + Shift + N keys


        • Incognito mode not save the history, but for me, in the most part of the time it's unnecessary.





        If you want use both (I recommend) you need enable AdGuard in Incognito Mode:




        1. On Chrome open Menu ( three lines on the right side)

        2. Go to More tools and then Extensions

        3. To turn the extension on, check the box. To turn off an extension, uncheck the enabled box.






        share|improve this answer


























          0












          0








          0







          Complementing what Damon said about the reasons for heavy loading due to advertisements and tracking, actualy i'm using some 'tricks' to minimize the problem with Facebook and other heavy sites.






          • AdGuard extension: Blocks all types of ads on all web pages, even on Facebook


          • AdBlock has many adBlockKillers, but does the same






          • Open Google Chrome on incognito mode using Ctrl + Shift + N keys


          • Incognito mode not save the history, but for me, in the most part of the time it's unnecessary.





          If you want use both (I recommend) you need enable AdGuard in Incognito Mode:




          1. On Chrome open Menu ( three lines on the right side)

          2. Go to More tools and then Extensions

          3. To turn the extension on, check the box. To turn off an extension, uncheck the enabled box.






          share|improve this answer













          Complementing what Damon said about the reasons for heavy loading due to advertisements and tracking, actualy i'm using some 'tricks' to minimize the problem with Facebook and other heavy sites.






          • AdGuard extension: Blocks all types of ads on all web pages, even on Facebook


          • AdBlock has many adBlockKillers, but does the same






          • Open Google Chrome on incognito mode using Ctrl + Shift + N keys


          • Incognito mode not save the history, but for me, in the most part of the time it's unnecessary.





          If you want use both (I recommend) you need enable AdGuard in Incognito Mode:




          1. On Chrome open Menu ( three lines on the right side)

          2. Go to More tools and then Extensions

          3. To turn the extension on, check the box. To turn off an extension, uncheck the enabled box.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 10 '18 at 0:55









          ℛɑƒæĿℛɑƒæĿ

          1035




          1035























              0














              I've seen the same sort of issue on my pc with Chrome & Facebook. Almost never see the problem with any other page. I operate with a dozen or so tabs always open, multitasking. I find that this even happens with a freshly-loaded Facebook page, left idle for a long period of time (like overnight, after I've gone to sleep).



              I've used "Process Explorer", a replacement for Task Manager (actually available from Microsoft) for years. Its advantage is...instead of giving just one listing for each program...you get individual listings for each process. This means, for instance, you can have a dozen (or more) for Chrome. It also allows you to "kill" individual processes.



              enter image description here



              My workaround (not really a solution) is to find the process in ProcessExplorer using the largest amount of memory (I sort the processes by amount of memory being used)...and kill it. This "kills" the facebook page (gives you a blank white "page died" window in that tab) without killing Chrome entirely, and releases the massive amount of memory FB had locked down...letting you reload FB. As you can see in this pic, FB is already using 700+megs...and I've had it open less than 30 minutes. If I leave it alone long enough, that number will climb 'til it's using every bit of available memory. I typically have to kill FB every 2-3 hours.



              UPDATE: Here's what it looks like after I left a freshly loaded instance of Facebook open and untouched over the weekend (3 days). While it's like that, pages are sluggish as heck to load, anything & everything on the computer is dog-slow. Killing that process that's taking up 2.5gb of memory...instantly brings everything back to life.
              enter image description here






              share|improve this answer






























                0














                I've seen the same sort of issue on my pc with Chrome & Facebook. Almost never see the problem with any other page. I operate with a dozen or so tabs always open, multitasking. I find that this even happens with a freshly-loaded Facebook page, left idle for a long period of time (like overnight, after I've gone to sleep).



                I've used "Process Explorer", a replacement for Task Manager (actually available from Microsoft) for years. Its advantage is...instead of giving just one listing for each program...you get individual listings for each process. This means, for instance, you can have a dozen (or more) for Chrome. It also allows you to "kill" individual processes.



                enter image description here



                My workaround (not really a solution) is to find the process in ProcessExplorer using the largest amount of memory (I sort the processes by amount of memory being used)...and kill it. This "kills" the facebook page (gives you a blank white "page died" window in that tab) without killing Chrome entirely, and releases the massive amount of memory FB had locked down...letting you reload FB. As you can see in this pic, FB is already using 700+megs...and I've had it open less than 30 minutes. If I leave it alone long enough, that number will climb 'til it's using every bit of available memory. I typically have to kill FB every 2-3 hours.



                UPDATE: Here's what it looks like after I left a freshly loaded instance of Facebook open and untouched over the weekend (3 days). While it's like that, pages are sluggish as heck to load, anything & everything on the computer is dog-slow. Killing that process that's taking up 2.5gb of memory...instantly brings everything back to life.
                enter image description here






                share|improve this answer




























                  0












                  0








                  0







                  I've seen the same sort of issue on my pc with Chrome & Facebook. Almost never see the problem with any other page. I operate with a dozen or so tabs always open, multitasking. I find that this even happens with a freshly-loaded Facebook page, left idle for a long period of time (like overnight, after I've gone to sleep).



                  I've used "Process Explorer", a replacement for Task Manager (actually available from Microsoft) for years. Its advantage is...instead of giving just one listing for each program...you get individual listings for each process. This means, for instance, you can have a dozen (or more) for Chrome. It also allows you to "kill" individual processes.



                  enter image description here



                  My workaround (not really a solution) is to find the process in ProcessExplorer using the largest amount of memory (I sort the processes by amount of memory being used)...and kill it. This "kills" the facebook page (gives you a blank white "page died" window in that tab) without killing Chrome entirely, and releases the massive amount of memory FB had locked down...letting you reload FB. As you can see in this pic, FB is already using 700+megs...and I've had it open less than 30 minutes. If I leave it alone long enough, that number will climb 'til it's using every bit of available memory. I typically have to kill FB every 2-3 hours.



                  UPDATE: Here's what it looks like after I left a freshly loaded instance of Facebook open and untouched over the weekend (3 days). While it's like that, pages are sluggish as heck to load, anything & everything on the computer is dog-slow. Killing that process that's taking up 2.5gb of memory...instantly brings everything back to life.
                  enter image description here






                  share|improve this answer















                  I've seen the same sort of issue on my pc with Chrome & Facebook. Almost never see the problem with any other page. I operate with a dozen or so tabs always open, multitasking. I find that this even happens with a freshly-loaded Facebook page, left idle for a long period of time (like overnight, after I've gone to sleep).



                  I've used "Process Explorer", a replacement for Task Manager (actually available from Microsoft) for years. Its advantage is...instead of giving just one listing for each program...you get individual listings for each process. This means, for instance, you can have a dozen (or more) for Chrome. It also allows you to "kill" individual processes.



                  enter image description here



                  My workaround (not really a solution) is to find the process in ProcessExplorer using the largest amount of memory (I sort the processes by amount of memory being used)...and kill it. This "kills" the facebook page (gives you a blank white "page died" window in that tab) without killing Chrome entirely, and releases the massive amount of memory FB had locked down...letting you reload FB. As you can see in this pic, FB is already using 700+megs...and I've had it open less than 30 minutes. If I leave it alone long enough, that number will climb 'til it's using every bit of available memory. I typically have to kill FB every 2-3 hours.



                  UPDATE: Here's what it looks like after I left a freshly loaded instance of Facebook open and untouched over the weekend (3 days). While it's like that, pages are sluggish as heck to load, anything & everything on the computer is dog-slow. Killing that process that's taking up 2.5gb of memory...instantly brings everything back to life.
                  enter image description here







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited May 20 '18 at 22:35

























                  answered May 16 '18 at 19:41









                  TheLandYachtTheLandYacht

                  12




                  12






























                      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.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1293546%2fwhy-running-facebook-on-google-chrome-uses-so-much-memory%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

                      Probability when a professor distributes a quiz and homework assignment to a class of n students.

                      Aardman Animations

                      Are they similar matrix