| 2009-02-20 11:33:36 |
Teodor Sobczak |
description |
Binary package hint: firefox-3.0
hi
Problem is very similar to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/267836
but point for keithieopia. That is not the same issue.
I'm running Ubuntu 8.10 with kernel 2.6.27-11,
GNOME 2.24.1
Xorg is 1:7.4
Firefox is 3.0.6
When entering particular pages(I can't post exact page but it was on facebook) whole system freezes. No response to to keyboard, mouse, or SysRq. It occures that firefox is making some application to go mad, which looks like this:
Feb 19 01:21:56 teo kernel: [46494.444059] Xorg invoked oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=0
Feb 19 01:21:56 teo kernel: [46494.444066] Pid: 16190, comm: Xorg Tainted: P 2.6.27-11-generic #1
Full message.log in attachment.
Waiting a while(10 minutes), or causing intensive memory use will force system to kill firefox. In log You can see that I unplugged and plugged in my USB Wireless card. That killed firefox. After restarting firefox and entering the same page(address was saved apparently) problem occurred again. |
Binary package hint: firefox-3.0
hi
I thought that problem is very similar to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/267836
but point for keithieopia. That is not the same issue.
I'm running Ubuntu 8.10 with kernel 2.6.27-11,
GNOME 2.24.1
Xorg is 1:7.4
Firefox is 3.0.6
When entering particular pages(I can't post exact page but it was on facebook) whole system freezes. No response to to keyboard, mouse, or SysRq. System monitor shows 100% of mem and CPU usage.(that is the only difference between this case and one I posted above).
Looks like my log is leftover after some other problem running my system and I was very lucky because that problem killed(?) firefox(after 10 minutes but still it's very kind of him :P). Something is invoking oom-killer constantly. I left my computer turned on during night with no intense memory use, and my log is full of oom-killer. Computer on the other hand did not freeze. That means that firefox is not leaving any info about its crash in logs.
|
|
