topic title: Google Chrome not running
Posts: 9
sukui
Joined: 18 Dec 2011
#1
Hi,

I installed the google chrome and ran without problem for the first time. But now when I try to open a page using the chrome it says" The following page(s) become unresponsive.You can wait for them to become responsive or kill them" The most interesting thing is that it always happens after I open the gmail.com. Befor opening it everything is working fine.
Thanks for your help.
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#2
What happens/error messages do you get when launching google chrome from terminal? I run Chromium from synaptic pkg manager.

Mine works OK though I get these error messages . Just my example.

Code: Select all

$ chromium
[2791:2825:529730382:ERROR:x509_certificate_nss.cc(810)] CERT_PKIXVerifyCert for www.google.com failed err=-8181
[2791:2858:541466663:ERROR:x509_certificate_nss.cc(596)] No EV Policy Tag
[2791:2854:567571327:ERROR:x509_certificate_nss.cc(810)] CERT_PKIXVerifyCert for mail.google.com failed err=-8181
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
I should also mention my cpu spikes up to 100% while opening Chromium while I have iceweasel opened at the same time while I am posting on this

Code: Select all

$ inxi
CPU~Single core Intel Pentium M (-UP-) clocked at 1595.057 Mhz Kernel~2.6.38-7.dmz.1-liquorix-686 i686 Up~17 min Mem~203.4/492.4MB HDD~30.0GB(28.6% used) Procs~92 Client~Shell inxi~1.7.27
Laptop.

Posts: 9
sukui
Joined: 18 Dec 2011
#3
HI,

thanks for your reply, but the owner of the laptop wanted to have the windows back, because she knows that better. So the antix was replaced by windows xp. But I'm happy that I know an op. system which doesn't require much memory __{{emoticon}}__
Posts: 11
fratermus
Joined: 15 Dec 2011
#4
IIRC chrom* runs background tasks when the browser is"closed" by default; this can be turned off in the prefs somewhere. On my box I've had to kill the chrom* processes, restart chrom* and disable background processes to make it stable. Was also chewing gobs of memory (100s of MB) with the backgrounded stuff running after I closed chrome.