Chromium on Debian Wheezy “Aw, Snap!” errorCan't install Google Chrome on amd64 WheezyChromium doesn't display Flash in Debian WheezyInstalling chromium-browser on Debian Wheezy Depends: chromium (>= 10) but it is not installableEvince / document viwer keeps changing my print settingsChrome/Chromium crashes (“Aw, snap!”, segfault): “Resource temporarily unavailable”dual boot problems windows 10 and debian jessieDebian with basic packagesDriver installation NVIDIA GeForce 940-mx not possibleUsing the chromium-widevine Debian packageContents of apt file revert at boot

Where else does the Shulchan Aruch quote an authority by name?

How to manage monthly salary

What is the offset in a seaplane's hull?

How can I fix this gap between bookcases I made?

What is the command to reset a PC without deleting any files

Is "plugging out" electronic devices an American expression?

When blogging recipes, how can I support both readers who want the narrative/journey and ones who want the printer-friendly recipe?

Can a planet have a different gravitational pull depending on its location in orbit around its sun?

What is it called when oen voice type sings a 'solo?'

Prime joint compound before latex paint?

Unbreakable Formation vs. Cry of the Carnarium

Can the Produce Flame cantrip be used to grapple, or as an unarmed strike, in the right circumstances?

Why did the Germans forbid the possession of pet pigeons in Rostov-on-Don in 1941?

How is it possible for user's password to be changed after storage was encrypted? (on OS X, Android)

Lied on resume at previous job

Is Social Media Science Fiction?

Domain expired, GoDaddy holds it and is asking more money

Is every set a filtered colimit of finite sets?

Is there a familial term for apples and pears?

What do you call something that goes against the spirit of the law, but is legal when interpreting the law to the letter?

Why do UK politicians seemingly ignore opinion polls on Brexit?

Is this food a bread or a loaf?

Ideas for 3rd eye abilities

What is GPS' 19 year rollover and does it present a cybersecurity issue?



Chromium on Debian Wheezy “Aw, Snap!” error


Can't install Google Chrome on amd64 WheezyChromium doesn't display Flash in Debian WheezyInstalling chromium-browser on Debian Wheezy Depends: chromium (>= 10) but it is not installableEvince / document viwer keeps changing my print settingsChrome/Chromium crashes (“Aw, snap!”, segfault): “Resource temporarily unavailable”dual boot problems windows 10 and debian jessieDebian with basic packagesDriver installation NVIDIA GeForce 940-mx not possibleUsing the chromium-widevine Debian packageContents of apt file revert at boot






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








3















My computer froze because of RAM exhaustion. I performed hard reset. When I launched Chromium, I was getting "Aw, Snap!" error on every page. So I deleted the folder .config/chromium/ and ran apt-get purge chromium and then rebooted and installed again. Unfortunately nothing changed. What should I do now?










share|improve this question






















  • Downgrade to a previous version of chrome.

    – Ipor Sircer
    Nov 2 '16 at 11:16











  • Do you have a lot of open tabs? I find that Chrome maxes out and gives a lot of "Aw, snap" errors around a hundred tabs on my machine, though not everywhere and all the time.

    – tripleee
    Apr 28 '17 at 14:54












  • What are your Debian and Chromium versions?

    – Paradox
    Apr 5 at 18:16











  • Debian 7.11, I can't tell the Chromium any more, since I have removed it

    – user965748
    2 days ago

















3















My computer froze because of RAM exhaustion. I performed hard reset. When I launched Chromium, I was getting "Aw, Snap!" error on every page. So I deleted the folder .config/chromium/ and ran apt-get purge chromium and then rebooted and installed again. Unfortunately nothing changed. What should I do now?










share|improve this question






















  • Downgrade to a previous version of chrome.

    – Ipor Sircer
    Nov 2 '16 at 11:16











  • Do you have a lot of open tabs? I find that Chrome maxes out and gives a lot of "Aw, snap" errors around a hundred tabs on my machine, though not everywhere and all the time.

    – tripleee
    Apr 28 '17 at 14:54












  • What are your Debian and Chromium versions?

    – Paradox
    Apr 5 at 18:16











  • Debian 7.11, I can't tell the Chromium any more, since I have removed it

    – user965748
    2 days ago













3












3








3








My computer froze because of RAM exhaustion. I performed hard reset. When I launched Chromium, I was getting "Aw, Snap!" error on every page. So I deleted the folder .config/chromium/ and ran apt-get purge chromium and then rebooted and installed again. Unfortunately nothing changed. What should I do now?










share|improve this question














My computer froze because of RAM exhaustion. I performed hard reset. When I launched Chromium, I was getting "Aw, Snap!" error on every page. So I deleted the folder .config/chromium/ and ran apt-get purge chromium and then rebooted and installed again. Unfortunately nothing changed. What should I do now?







linux debian chrome






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 2 '16 at 11:15









user965748user965748

5129




5129












  • Downgrade to a previous version of chrome.

    – Ipor Sircer
    Nov 2 '16 at 11:16











  • Do you have a lot of open tabs? I find that Chrome maxes out and gives a lot of "Aw, snap" errors around a hundred tabs on my machine, though not everywhere and all the time.

    – tripleee
    Apr 28 '17 at 14:54












  • What are your Debian and Chromium versions?

    – Paradox
    Apr 5 at 18:16











  • Debian 7.11, I can't tell the Chromium any more, since I have removed it

    – user965748
    2 days ago

















  • Downgrade to a previous version of chrome.

    – Ipor Sircer
    Nov 2 '16 at 11:16











  • Do you have a lot of open tabs? I find that Chrome maxes out and gives a lot of "Aw, snap" errors around a hundred tabs on my machine, though not everywhere and all the time.

    – tripleee
    Apr 28 '17 at 14:54












  • What are your Debian and Chromium versions?

    – Paradox
    Apr 5 at 18:16











  • Debian 7.11, I can't tell the Chromium any more, since I have removed it

    – user965748
    2 days ago
















Downgrade to a previous version of chrome.

– Ipor Sircer
Nov 2 '16 at 11:16





Downgrade to a previous version of chrome.

– Ipor Sircer
Nov 2 '16 at 11:16













Do you have a lot of open tabs? I find that Chrome maxes out and gives a lot of "Aw, snap" errors around a hundred tabs on my machine, though not everywhere and all the time.

– tripleee
Apr 28 '17 at 14:54






Do you have a lot of open tabs? I find that Chrome maxes out and gives a lot of "Aw, snap" errors around a hundred tabs on my machine, though not everywhere and all the time.

– tripleee
Apr 28 '17 at 14:54














What are your Debian and Chromium versions?

– Paradox
Apr 5 at 18:16





What are your Debian and Chromium versions?

– Paradox
Apr 5 at 18:16













Debian 7.11, I can't tell the Chromium any more, since I have removed it

– user965748
2 days ago





Debian 7.11, I can't tell the Chromium any more, since I have removed it

– user965748
2 days ago










4 Answers
4






active

oldest

votes


















0














Did you recently have a software upgrade, including the kernel?? I had one a couple of days ago. It was about 160 megs worth of updates. After that I got the "Aw Snap" message in Chromium as well. I uninstalled it, removed the cache and config files, reinstalled it and nothing has changed.



I'm in the same boat.



Part II



I don't think I've ever had RAM exhaustion, so I can't offer an answer for that. My usage is probably a lot different than yours. I run Bleachbit at least once a day to clear out my cache files, etc.



I decided to start over with a fresh install of Wheezy.



I first backed up my home directory on an external HD with the command:



tar -pczf home.tar.gz /home


I then reinstalled Wheezy from the original iso disc I created two years ago.



After it was installed, I checked Chromium and it worked fine. I reset my preferences and continued as usual.



After 24 hours, I got an update notice for 350 megs worth of updates. This was for the kernel plus a bunch of other stuff. Previously, the updates occurred over a longer time period, but now it jumps to the newer stuff. I downloaded and installed them.



After the updates, I discovered that Chromium was getting the "Aw Snap" message again, so I'm assuming that the problem is in the updates somewhere.



My theory is once Wheezy updates past a certain point, Chromium stops working (37.0.2062.120-1). You have to move on to Jessie with a newer version of Chromium to keep using it. Or else find a way to install the Jessie/Chromium version on Wheezy.



Part III



The above answers only apply to the 32 bit Wheezy running on an amd64 machine (long story).



I just updated to the amd64 version of Wheezy on the same machine.



I opened Chromium and got the "Aw Snap" message again right out of the gate; no RAM exhaustion or updates needed.



I figure since I'm running a 64 bit OS now, I can just install Google Chrome and not bother with Chromium. I downloaded and tried to install it with GDebi but got the following message:



Error: Dependency is not satisfiable: libstdc++6(>=4.8.0)



Google only ended support for the 32 bit Wheezy, so why is 64 bit getting this message??



I'll probably ask this as a new question.



Part IV



Here's my question:
Can't install Google Chrome on amd64 Wheezy






share|improve this answer
































    0














    Answer/Comment



    I'm wondering if you've tried installing chromium from the wheezy backports. Maybe that version works? Put



    deb http://ftp.debian.org/debian wheezy-backports main



    In your sources.list and then download chromium again. (after purging) You should probably delete your current package lists and comment out your other sources before updating/upgrading, to avoid any conflicts.



    What sucks about google chrome is there aren't really error logs unless you enable crash reports and those get sent to google.



    What does uname -a say for you? And what version of Chromium are you using? These things are important if you want to file a bug report.



    My other suggestion is to just download the tarball [Warning - it's over 2GB]
    It's probably more recent than your .deb (debian's chromium package)






    share|improve this answer

























    • uname -a: Linux michal 3.2.0-4-amd64 #1 SMP Debian 3.2.82-1 x86_64 GNU/Linux and Chromium version is chromium_37.0.2062.120-1~deb7u1_amd64.deb

      – user965748
      Nov 4 '16 at 0:27











    • Did you try any of my suggestions?

      – trudgemank
      Nov 4 '16 at 5:56


















    0














    The next time your system freezes from memory exhaustion, you can try invoking the OOM killer manually before resorting to a hard reset.



    1) Add or change kernel.sysrq=1 to /etc/sysctl.conf and run sysctl -p.



    2) When the system is out of memory, press Alt+SysRq+f to kill a process.






    share|improve this answer






























      0














      Chrome uses a lot of RAM while running. To fix this issue, create some swap space on your hard drive by creating a new partition using fdisk/gdisk/parted/whatever then create a swap filesystem on that partition



      mkswap /dev/sdX


      assuming /dev/sdX is the partition you created.
      Next, enable the swap space



      swapon /dev/sdX


      Finally, add a line to /etc/fstab to mount the swap space automatically on boot



      /dev/sdX none swap defaults 0 0


      Execute the command mount -a to mount the swap space



      This partition will hold data that was in memory when there is no memory left. It is like extending RAM but with slower access.






      share|improve this answer























        protected by Community Nov 14 '16 at 16:26



        Thank you for your interest in this question.
        Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



        Would you like to answer one of these unanswered questions instead?














        4 Answers
        4






        active

        oldest

        votes








        4 Answers
        4






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        0














        Did you recently have a software upgrade, including the kernel?? I had one a couple of days ago. It was about 160 megs worth of updates. After that I got the "Aw Snap" message in Chromium as well. I uninstalled it, removed the cache and config files, reinstalled it and nothing has changed.



        I'm in the same boat.



        Part II



        I don't think I've ever had RAM exhaustion, so I can't offer an answer for that. My usage is probably a lot different than yours. I run Bleachbit at least once a day to clear out my cache files, etc.



        I decided to start over with a fresh install of Wheezy.



        I first backed up my home directory on an external HD with the command:



        tar -pczf home.tar.gz /home


        I then reinstalled Wheezy from the original iso disc I created two years ago.



        After it was installed, I checked Chromium and it worked fine. I reset my preferences and continued as usual.



        After 24 hours, I got an update notice for 350 megs worth of updates. This was for the kernel plus a bunch of other stuff. Previously, the updates occurred over a longer time period, but now it jumps to the newer stuff. I downloaded and installed them.



        After the updates, I discovered that Chromium was getting the "Aw Snap" message again, so I'm assuming that the problem is in the updates somewhere.



        My theory is once Wheezy updates past a certain point, Chromium stops working (37.0.2062.120-1). You have to move on to Jessie with a newer version of Chromium to keep using it. Or else find a way to install the Jessie/Chromium version on Wheezy.



        Part III



        The above answers only apply to the 32 bit Wheezy running on an amd64 machine (long story).



        I just updated to the amd64 version of Wheezy on the same machine.



        I opened Chromium and got the "Aw Snap" message again right out of the gate; no RAM exhaustion or updates needed.



        I figure since I'm running a 64 bit OS now, I can just install Google Chrome and not bother with Chromium. I downloaded and tried to install it with GDebi but got the following message:



        Error: Dependency is not satisfiable: libstdc++6(>=4.8.0)



        Google only ended support for the 32 bit Wheezy, so why is 64 bit getting this message??



        I'll probably ask this as a new question.



        Part IV



        Here's my question:
        Can't install Google Chrome on amd64 Wheezy






        share|improve this answer





























          0














          Did you recently have a software upgrade, including the kernel?? I had one a couple of days ago. It was about 160 megs worth of updates. After that I got the "Aw Snap" message in Chromium as well. I uninstalled it, removed the cache and config files, reinstalled it and nothing has changed.



          I'm in the same boat.



          Part II



          I don't think I've ever had RAM exhaustion, so I can't offer an answer for that. My usage is probably a lot different than yours. I run Bleachbit at least once a day to clear out my cache files, etc.



          I decided to start over with a fresh install of Wheezy.



          I first backed up my home directory on an external HD with the command:



          tar -pczf home.tar.gz /home


          I then reinstalled Wheezy from the original iso disc I created two years ago.



          After it was installed, I checked Chromium and it worked fine. I reset my preferences and continued as usual.



          After 24 hours, I got an update notice for 350 megs worth of updates. This was for the kernel plus a bunch of other stuff. Previously, the updates occurred over a longer time period, but now it jumps to the newer stuff. I downloaded and installed them.



          After the updates, I discovered that Chromium was getting the "Aw Snap" message again, so I'm assuming that the problem is in the updates somewhere.



          My theory is once Wheezy updates past a certain point, Chromium stops working (37.0.2062.120-1). You have to move on to Jessie with a newer version of Chromium to keep using it. Or else find a way to install the Jessie/Chromium version on Wheezy.



          Part III



          The above answers only apply to the 32 bit Wheezy running on an amd64 machine (long story).



          I just updated to the amd64 version of Wheezy on the same machine.



          I opened Chromium and got the "Aw Snap" message again right out of the gate; no RAM exhaustion or updates needed.



          I figure since I'm running a 64 bit OS now, I can just install Google Chrome and not bother with Chromium. I downloaded and tried to install it with GDebi but got the following message:



          Error: Dependency is not satisfiable: libstdc++6(>=4.8.0)



          Google only ended support for the 32 bit Wheezy, so why is 64 bit getting this message??



          I'll probably ask this as a new question.



          Part IV



          Here's my question:
          Can't install Google Chrome on amd64 Wheezy






          share|improve this answer



























            0












            0








            0







            Did you recently have a software upgrade, including the kernel?? I had one a couple of days ago. It was about 160 megs worth of updates. After that I got the "Aw Snap" message in Chromium as well. I uninstalled it, removed the cache and config files, reinstalled it and nothing has changed.



            I'm in the same boat.



            Part II



            I don't think I've ever had RAM exhaustion, so I can't offer an answer for that. My usage is probably a lot different than yours. I run Bleachbit at least once a day to clear out my cache files, etc.



            I decided to start over with a fresh install of Wheezy.



            I first backed up my home directory on an external HD with the command:



            tar -pczf home.tar.gz /home


            I then reinstalled Wheezy from the original iso disc I created two years ago.



            After it was installed, I checked Chromium and it worked fine. I reset my preferences and continued as usual.



            After 24 hours, I got an update notice for 350 megs worth of updates. This was for the kernel plus a bunch of other stuff. Previously, the updates occurred over a longer time period, but now it jumps to the newer stuff. I downloaded and installed them.



            After the updates, I discovered that Chromium was getting the "Aw Snap" message again, so I'm assuming that the problem is in the updates somewhere.



            My theory is once Wheezy updates past a certain point, Chromium stops working (37.0.2062.120-1). You have to move on to Jessie with a newer version of Chromium to keep using it. Or else find a way to install the Jessie/Chromium version on Wheezy.



            Part III



            The above answers only apply to the 32 bit Wheezy running on an amd64 machine (long story).



            I just updated to the amd64 version of Wheezy on the same machine.



            I opened Chromium and got the "Aw Snap" message again right out of the gate; no RAM exhaustion or updates needed.



            I figure since I'm running a 64 bit OS now, I can just install Google Chrome and not bother with Chromium. I downloaded and tried to install it with GDebi but got the following message:



            Error: Dependency is not satisfiable: libstdc++6(>=4.8.0)



            Google only ended support for the 32 bit Wheezy, so why is 64 bit getting this message??



            I'll probably ask this as a new question.



            Part IV



            Here's my question:
            Can't install Google Chrome on amd64 Wheezy






            share|improve this answer















            Did you recently have a software upgrade, including the kernel?? I had one a couple of days ago. It was about 160 megs worth of updates. After that I got the "Aw Snap" message in Chromium as well. I uninstalled it, removed the cache and config files, reinstalled it and nothing has changed.



            I'm in the same boat.



            Part II



            I don't think I've ever had RAM exhaustion, so I can't offer an answer for that. My usage is probably a lot different than yours. I run Bleachbit at least once a day to clear out my cache files, etc.



            I decided to start over with a fresh install of Wheezy.



            I first backed up my home directory on an external HD with the command:



            tar -pczf home.tar.gz /home


            I then reinstalled Wheezy from the original iso disc I created two years ago.



            After it was installed, I checked Chromium and it worked fine. I reset my preferences and continued as usual.



            After 24 hours, I got an update notice for 350 megs worth of updates. This was for the kernel plus a bunch of other stuff. Previously, the updates occurred over a longer time period, but now it jumps to the newer stuff. I downloaded and installed them.



            After the updates, I discovered that Chromium was getting the "Aw Snap" message again, so I'm assuming that the problem is in the updates somewhere.



            My theory is once Wheezy updates past a certain point, Chromium stops working (37.0.2062.120-1). You have to move on to Jessie with a newer version of Chromium to keep using it. Or else find a way to install the Jessie/Chromium version on Wheezy.



            Part III



            The above answers only apply to the 32 bit Wheezy running on an amd64 machine (long story).



            I just updated to the amd64 version of Wheezy on the same machine.



            I opened Chromium and got the "Aw Snap" message again right out of the gate; no RAM exhaustion or updates needed.



            I figure since I'm running a 64 bit OS now, I can just install Google Chrome and not bother with Chromium. I downloaded and tried to install it with GDebi but got the following message:



            Error: Dependency is not satisfiable: libstdc++6(>=4.8.0)



            Google only ended support for the 32 bit Wheezy, so why is 64 bit getting this message??



            I'll probably ask this as a new question.



            Part IV



            Here's my question:
            Can't install Google Chrome on amd64 Wheezy







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Nov 17 '16 at 13:40









            Sedulous

            125




            125










            answered Nov 11 '16 at 16:03









            SedulousSedulous

            11




            11























                0














                Answer/Comment



                I'm wondering if you've tried installing chromium from the wheezy backports. Maybe that version works? Put



                deb http://ftp.debian.org/debian wheezy-backports main



                In your sources.list and then download chromium again. (after purging) You should probably delete your current package lists and comment out your other sources before updating/upgrading, to avoid any conflicts.



                What sucks about google chrome is there aren't really error logs unless you enable crash reports and those get sent to google.



                What does uname -a say for you? And what version of Chromium are you using? These things are important if you want to file a bug report.



                My other suggestion is to just download the tarball [Warning - it's over 2GB]
                It's probably more recent than your .deb (debian's chromium package)






                share|improve this answer

























                • uname -a: Linux michal 3.2.0-4-amd64 #1 SMP Debian 3.2.82-1 x86_64 GNU/Linux and Chromium version is chromium_37.0.2062.120-1~deb7u1_amd64.deb

                  – user965748
                  Nov 4 '16 at 0:27











                • Did you try any of my suggestions?

                  – trudgemank
                  Nov 4 '16 at 5:56















                0














                Answer/Comment



                I'm wondering if you've tried installing chromium from the wheezy backports. Maybe that version works? Put



                deb http://ftp.debian.org/debian wheezy-backports main



                In your sources.list and then download chromium again. (after purging) You should probably delete your current package lists and comment out your other sources before updating/upgrading, to avoid any conflicts.



                What sucks about google chrome is there aren't really error logs unless you enable crash reports and those get sent to google.



                What does uname -a say for you? And what version of Chromium are you using? These things are important if you want to file a bug report.



                My other suggestion is to just download the tarball [Warning - it's over 2GB]
                It's probably more recent than your .deb (debian's chromium package)






                share|improve this answer

























                • uname -a: Linux michal 3.2.0-4-amd64 #1 SMP Debian 3.2.82-1 x86_64 GNU/Linux and Chromium version is chromium_37.0.2062.120-1~deb7u1_amd64.deb

                  – user965748
                  Nov 4 '16 at 0:27











                • Did you try any of my suggestions?

                  – trudgemank
                  Nov 4 '16 at 5:56













                0












                0








                0







                Answer/Comment



                I'm wondering if you've tried installing chromium from the wheezy backports. Maybe that version works? Put



                deb http://ftp.debian.org/debian wheezy-backports main



                In your sources.list and then download chromium again. (after purging) You should probably delete your current package lists and comment out your other sources before updating/upgrading, to avoid any conflicts.



                What sucks about google chrome is there aren't really error logs unless you enable crash reports and those get sent to google.



                What does uname -a say for you? And what version of Chromium are you using? These things are important if you want to file a bug report.



                My other suggestion is to just download the tarball [Warning - it's over 2GB]
                It's probably more recent than your .deb (debian's chromium package)






                share|improve this answer















                Answer/Comment



                I'm wondering if you've tried installing chromium from the wheezy backports. Maybe that version works? Put



                deb http://ftp.debian.org/debian wheezy-backports main



                In your sources.list and then download chromium again. (after purging) You should probably delete your current package lists and comment out your other sources before updating/upgrading, to avoid any conflicts.



                What sucks about google chrome is there aren't really error logs unless you enable crash reports and those get sent to google.



                What does uname -a say for you? And what version of Chromium are you using? These things are important if you want to file a bug report.



                My other suggestion is to just download the tarball [Warning - it's over 2GB]
                It's probably more recent than your .deb (debian's chromium package)







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Apr 28 '17 at 13:31









                Stephen Rauch

                3,354101529




                3,354101529










                answered Nov 3 '16 at 7:24









                trudgemanktrudgemank

                12717




                12717












                • uname -a: Linux michal 3.2.0-4-amd64 #1 SMP Debian 3.2.82-1 x86_64 GNU/Linux and Chromium version is chromium_37.0.2062.120-1~deb7u1_amd64.deb

                  – user965748
                  Nov 4 '16 at 0:27











                • Did you try any of my suggestions?

                  – trudgemank
                  Nov 4 '16 at 5:56

















                • uname -a: Linux michal 3.2.0-4-amd64 #1 SMP Debian 3.2.82-1 x86_64 GNU/Linux and Chromium version is chromium_37.0.2062.120-1~deb7u1_amd64.deb

                  – user965748
                  Nov 4 '16 at 0:27











                • Did you try any of my suggestions?

                  – trudgemank
                  Nov 4 '16 at 5:56
















                uname -a: Linux michal 3.2.0-4-amd64 #1 SMP Debian 3.2.82-1 x86_64 GNU/Linux and Chromium version is chromium_37.0.2062.120-1~deb7u1_amd64.deb

                – user965748
                Nov 4 '16 at 0:27





                uname -a: Linux michal 3.2.0-4-amd64 #1 SMP Debian 3.2.82-1 x86_64 GNU/Linux and Chromium version is chromium_37.0.2062.120-1~deb7u1_amd64.deb

                – user965748
                Nov 4 '16 at 0:27













                Did you try any of my suggestions?

                – trudgemank
                Nov 4 '16 at 5:56





                Did you try any of my suggestions?

                – trudgemank
                Nov 4 '16 at 5:56











                0














                The next time your system freezes from memory exhaustion, you can try invoking the OOM killer manually before resorting to a hard reset.



                1) Add or change kernel.sysrq=1 to /etc/sysctl.conf and run sysctl -p.



                2) When the system is out of memory, press Alt+SysRq+f to kill a process.






                share|improve this answer



























                  0














                  The next time your system freezes from memory exhaustion, you can try invoking the OOM killer manually before resorting to a hard reset.



                  1) Add or change kernel.sysrq=1 to /etc/sysctl.conf and run sysctl -p.



                  2) When the system is out of memory, press Alt+SysRq+f to kill a process.






                  share|improve this answer

























                    0












                    0








                    0







                    The next time your system freezes from memory exhaustion, you can try invoking the OOM killer manually before resorting to a hard reset.



                    1) Add or change kernel.sysrq=1 to /etc/sysctl.conf and run sysctl -p.



                    2) When the system is out of memory, press Alt+SysRq+f to kill a process.






                    share|improve this answer













                    The next time your system freezes from memory exhaustion, you can try invoking the OOM killer manually before resorting to a hard reset.



                    1) Add or change kernel.sysrq=1 to /etc/sysctl.conf and run sysctl -p.



                    2) When the system is out of memory, press Alt+SysRq+f to kill a process.







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Feb 26 '18 at 2:34









                    dsstorefile1dsstorefile1

                    1,802314




                    1,802314





















                        0














                        Chrome uses a lot of RAM while running. To fix this issue, create some swap space on your hard drive by creating a new partition using fdisk/gdisk/parted/whatever then create a swap filesystem on that partition



                        mkswap /dev/sdX


                        assuming /dev/sdX is the partition you created.
                        Next, enable the swap space



                        swapon /dev/sdX


                        Finally, add a line to /etc/fstab to mount the swap space automatically on boot



                        /dev/sdX none swap defaults 0 0


                        Execute the command mount -a to mount the swap space



                        This partition will hold data that was in memory when there is no memory left. It is like extending RAM but with slower access.






                        share|improve this answer





























                          0














                          Chrome uses a lot of RAM while running. To fix this issue, create some swap space on your hard drive by creating a new partition using fdisk/gdisk/parted/whatever then create a swap filesystem on that partition



                          mkswap /dev/sdX


                          assuming /dev/sdX is the partition you created.
                          Next, enable the swap space



                          swapon /dev/sdX


                          Finally, add a line to /etc/fstab to mount the swap space automatically on boot



                          /dev/sdX none swap defaults 0 0


                          Execute the command mount -a to mount the swap space



                          This partition will hold data that was in memory when there is no memory left. It is like extending RAM but with slower access.






                          share|improve this answer



























                            0












                            0








                            0







                            Chrome uses a lot of RAM while running. To fix this issue, create some swap space on your hard drive by creating a new partition using fdisk/gdisk/parted/whatever then create a swap filesystem on that partition



                            mkswap /dev/sdX


                            assuming /dev/sdX is the partition you created.
                            Next, enable the swap space



                            swapon /dev/sdX


                            Finally, add a line to /etc/fstab to mount the swap space automatically on boot



                            /dev/sdX none swap defaults 0 0


                            Execute the command mount -a to mount the swap space



                            This partition will hold data that was in memory when there is no memory left. It is like extending RAM but with slower access.






                            share|improve this answer















                            Chrome uses a lot of RAM while running. To fix this issue, create some swap space on your hard drive by creating a new partition using fdisk/gdisk/parted/whatever then create a swap filesystem on that partition



                            mkswap /dev/sdX


                            assuming /dev/sdX is the partition you created.
                            Next, enable the swap space



                            swapon /dev/sdX


                            Finally, add a line to /etc/fstab to mount the swap space automatically on boot



                            /dev/sdX none swap defaults 0 0


                            Execute the command mount -a to mount the swap space



                            This partition will hold data that was in memory when there is no memory left. It is like extending RAM but with slower access.







                            share|improve this answer














                            share|improve this answer



                            share|improve this answer








                            edited Apr 5 at 23:35









                            Rui F Ribeiro

                            42k1483142




                            42k1483142










                            answered Nov 11 '16 at 18:14









                            vespidvespid

                            1696




                            1696















                                protected by Community Nov 14 '16 at 16:26



                                Thank you for your interest in this question.
                                Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                                Would you like to answer one of these unanswered questions instead?



                                Popular posts from this blog

                                getting Checkpoint VPN SSL Network Extender working in the command lineHow to connect to CheckPoint VPN on Ubuntu 18.04LTS?Will the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayVPN SSL Network Extender in FirefoxLinux Checkpoint SNX tool configuration issuesCheck Point - Connect under Linux - snx + OTPSNX VPN Ububuntu 18.XXUsing Checkpoint VPN SSL Network Extender CLI with certificateVPN with network manager (nm-applet) is not workingWill the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayImport VPN config files to NetworkManager from command lineTrouble connecting to VPN using network-manager, while command line worksStart a VPN connection with PPTP protocol on command linestarting a docker service daemon breaks the vpn networkCan't connect to vpn with Network-managerVPN SSL Network Extender in FirefoxUsing Checkpoint VPN SSL Network Extender CLI with certificate

                                Cannot Extend partition with GParted The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsCan't increase partition size with GParted?GParted doesn't recognize the unallocated space after my current partitionWhat is the best way to add unallocated space located before to Ubuntu 12.04 partition with GParted live?I can't figure out how to extend my Arch home partition into free spaceGparted Linux Mint 18.1 issueTrying to extend but swap partition is showing as Unknown in Gparted, shows proper from fdiskRearrange partitions in gparted to extend a partitionUnable to extend partition even though unallocated space is next to it using GPartedAllocate free space to root partitiongparted: how to merge unallocated space with a partition

                                Marilyn Monroe Ny fiainany manokana | Jereo koa | Meny fitetezanafanitarana azy.