Changed title, as I verified that this is not a regression and happens even with previous 2.6.32 kernels.
I experience the freeze every time I do the following:
1) Go online (I have only tried with ppp dialup on GPRS mobile)
2) Start google-chrome
3) Browse some pages
4) Exit google-chrome
on exit I get the hard freeze.
I have the same behavior both on a desktop with AMD Phenom II cpu and nvidia graphis (with proprietary drivers) and a Dell Laptop with Intel Core II processor and Intel graphics. Both are 64 bit lucid.
In all cases, the system becomes unresponsive (even to SysReq magic) and unreachable from the net.
This thing is well documented from other web sites. See:
It has never been reported as an ubuntu bug, since who noticed it regarded it as a google-chrome bug.
Personally I think that this is a kernel bug that google-chrome happens to trigger. The notice (in some of the previous websites) that downgrading to 2.6.32-rc7 fixes the issue appears as an additional hint that this may be the case.
Of course there can be bugs in google-chrome and even serious ones, but by no means these should bring a system to a complete halt in this way.
Changed title, as I verified that this is not a regression and happens even with previous 2.6.32 kernels.
I experience the freeze every time I do the following:
1) Go online (I have only tried with ppp dialup on GPRS mobile)
2) Start google-chrome
3) Browse some pages
4) Exit google-chrome
on exit I get the hard freeze.
I have the same behavior both on a desktop with AMD Phenom II cpu and nvidia graphis (with proprietary drivers) and a Dell Laptop with Intel Core II processor and Intel graphics. Both are 64 bit lucid.
In all cases, the system becomes unresponsive (even to SysReq magic) and unreachable from the net.
This thing is well documented from other web sites. See:
http:// www.google. com/support/ forum/p/ Chrome/ thread? tid=7493a9fc196 ea8be&hl= en ubuntuforums. org/showthread. php?s=871a4db71 d2354a920c8694c 472e6a56& t=1470623
http://
It has never been reported as an ubuntu bug, since who noticed it regarded it as a google-chrome bug.
Personally I think that this is a kernel bug that google-chrome happens to trigger. The notice (in some of the previous websites) that downgrading to 2.6.32-rc7 fixes the issue appears as an additional hint that this may be the case.
Of course there can be bugs in google-chrome and even serious ones, but by no means these should bring a system to a complete halt in this way.