[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

system killing konqueror process overnight to free memory, why?



Problem with system killing a konqueror session from time to time while not in 
use or low usage.  System runs 24/7, has a fairly busy kmail usage, has 
multiple konqueror browser windows with quite a few tabs open in each window, 
during this last instance Mozilla composer was also open, as well as some 
bash shells, kwrite, ktimer, kontact/kmail, and a few minor applets on the 
kicker panel.  The box is logged into from another desktop on the lan, and is 
basically used as a file server and to run the above applications daily.

It's a Debian Sarge install kept up to date, relevant info just below, syslog 
at bottom showing system killing konqueror session with largest number of 
tabs open.  What caused the system to kill the konqueror process, and how to 
prevent in future?

Thanks, 
Laszlo

ps, I know I have too much swap.


# uptime
 08:02:44 up 70 days, 54 min,  3 users,  load average: 0.10, 0.15, 0.11

# free
               total       used       free     shared    buffers     cached
Mem:   516336     510196       6140          0      34980     101176
-/+ buffers/cache:     374040     142296
Swap:      3919696     748496    3171200

Linux debian 2.6.11-1-k7 #1 Mon Jun 20 21:26:23 MDT 2005 i686 GNU/Linux

Dec 22 06:37:08 debian kernel: oom-killer: gfp_mask=0xd0
Dec 22 06:37:09 debian kernel: DMA per-cpu:
Dec 22 06:37:09 debian kernel: cpu 0 hot: low 2, high 6, batch 1
Dec 22 06:37:09 debian kernel: cpu 0 cold: low 0, high 2, batch 1
Dec 22 06:37:09 debian kernel: Normal per-cpu:
Dec 22 06:37:09 debian kernel: cpu 0 hot: low 32, high 96, batch 16
Dec 22 06:37:09 debian kernel: cpu 0 cold: low 0, high 32, batch 16
Dec 22 06:37:09 debian kernel: HighMem per-cpu: empty
Dec 22 06:37:09 debian kernel:
Dec 22 06:37:09 debian kernel: Free pages:        6044kB (0kB HighMem)
Dec 22 06:37:09 debian kernel: Active:90848 inactive:11955 dirty:111 
writeback:223 unstable:0 free:1511 sl
ab:17905 mapped:93053 pagetables:1284
Dec 22 06:37:09 debian kernel: DMA free:2068kB min:88kB low:108kB high:132kB 
active:11020kB inactive:0kB p
resent:16384kB pages_scanned:60558 all_unreclaimable? yes
Dec 22 06:37:09 debian kernel: lowmem_reserve[]: 0 495 495
Dec 22 06:37:09 debian kernel: Normal free:3976kB min:2804kB low:3504kB 
high:4204kB active:352372kB inacti
ve:47820kB present:507824kB pages_scanned:174 all_unreclaimable? no
Dec 22 06:37:09 debian kernel: lowmem_reserve[]: 0 0 0
Dec 22 06:37:09 debian kernel: HighMem free:0kB min:128kB low:160kB high:192kB 
active:0kB inactive:0kB pre
sent:0kB pages_scanned:0 all_unreclaimable? no
Dec 22 06:37:09 debian kernel: lowmem_reserve[]: 0 0 0
Dec 22 06:37:09 debian kernel: DMA: 1*4kB 0*8kB 1*16kB 2*32kB 3*64kB 0*128kB 
1*256kB 1*512kB 1*1024kB 0*20
48kB 0*4096kB = 2068kB
Dec 22 06:37:09 debian kernel: Normal: 304*4kB 9*8kB 12*16kB 10*32kB 6*64kB 
2*128kB 0*256kB 1*512kB 1*1024
kB 0*2048kB 0*4096kB = 3976kB
Dec 22 06:37:09 debian kernel: HighMem: empty
Dec 22 06:37:09 debian kernel: Swap cache: add 23635233, delete 23578367, find 
10279467/14435889, race 1+5
3
Dec 22 06:37:09 debian kernel: Free swap  = 3043352kB
Dec 22 06:37:09 debian kernel: Total swap = 3919696kB
Dec 22 06:37:09 debian kernel: Out of Memory: Killed process 465 (konqueror).


Dec 22 06:38:47 debian syslogd 1.4.1#17: restart.
Dec 22 06:38:49 debian wwwoffled[28651]: WWWOFFLE Connection from host 
localhost (127.0.0.1).
Dec 22 06:38:49 debian wwwoffled[28651]: WWWOFFLE Status.
Dec 22 06:38:49 debian wwwoffled[28651]: WWWOFFLE Connection from host 
localhost (127.0.0.1).
Dec 22 06:38:49 debian wwwoffled[21929]: WWWOFFLE Purge.
Dec 22 06:38:49 debian wwwoffled[21929]: The number of blocks (0) looks wrong; 
using 1024 for blocksize.
Dec 22 06:38:49 debian wwwoffled[21929]: WWWOFFLE Purge finished.


-- 
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Taper shank drills, silver & deming drills, surface treated high speed steel 
jobbers length drills, http://www.bluebaysupply.com



Reply to: