vorpal
12-27-02, 05:34 AM
Hi.
Sometimes after opening an application, the system slows to a crawl for about 1 to 2 minutes, then returns to normal. Mouse movement becomes jerky, redrawing the desktop background can take many seconds, etc.
This is always reproducible by starting X and then opening eg. several console windows, or instances of konqueror. Once the slowdown occurs, no new applications will open.
At this point, even running 'vi' in a terminal results in an unceremonious (and immediate) "segmetation fault" !!
Switching to a console (ctr+alt+f2) running top, I find that one or more recently started processes has started to gobble up huge amounts of memory. 200M, 400M, 600M, rapidly increasing. The processor usage is at 100%, divided between the rogue processes and kswapd.
The processes reach a size of 2000M and either crash, or in some cases, suddenly return to normal memory usage, releasing all the used memory. The slowdown stops.
This problem occurs occaisionally under drivers 2960 and 3123, and only when several applications are running.
However, under 4191, this slowdown can happen opening even one application, and sometimes even while KDE is starting.
Reverting to the kernel driver fixes the problem. I can open zillions of windows, no probs.
Is this a memory leak?
Might it be due to the race condition in the module's interface code?
Is this related to the troubles people are having with slowdowns in Nautilus? Has some Nautilus person checked memory usage during slowdowns?
Is this likely to be fixed by the patches at www.minion.de? What do they do and who should use them? Do they work with 2.4 kernels?
The system is:
-Mandrake 9
-kernel 2.4.19-16mdkenterprise (compiled with 4G -mem support, I believe)
-XFree 4.2
-gcc 3.2
-KDE 3.0.3 (I'll try it under gnome)
-using .src.rpm versions 4191, 3123, 2960
-Athlon 1700
-1G ram, 6G swap
-64M GF2MX400
Thankyou,
jvf
Sometimes after opening an application, the system slows to a crawl for about 1 to 2 minutes, then returns to normal. Mouse movement becomes jerky, redrawing the desktop background can take many seconds, etc.
This is always reproducible by starting X and then opening eg. several console windows, or instances of konqueror. Once the slowdown occurs, no new applications will open.
At this point, even running 'vi' in a terminal results in an unceremonious (and immediate) "segmetation fault" !!
Switching to a console (ctr+alt+f2) running top, I find that one or more recently started processes has started to gobble up huge amounts of memory. 200M, 400M, 600M, rapidly increasing. The processor usage is at 100%, divided between the rogue processes and kswapd.
The processes reach a size of 2000M and either crash, or in some cases, suddenly return to normal memory usage, releasing all the used memory. The slowdown stops.
This problem occurs occaisionally under drivers 2960 and 3123, and only when several applications are running.
However, under 4191, this slowdown can happen opening even one application, and sometimes even while KDE is starting.
Reverting to the kernel driver fixes the problem. I can open zillions of windows, no probs.
Is this a memory leak?
Might it be due to the race condition in the module's interface code?
Is this related to the troubles people are having with slowdowns in Nautilus? Has some Nautilus person checked memory usage during slowdowns?
Is this likely to be fixed by the patches at www.minion.de? What do they do and who should use them? Do they work with 2.4 kernels?
The system is:
-Mandrake 9
-kernel 2.4.19-16mdkenterprise (compiled with 4G -mem support, I believe)
-XFree 4.2
-gcc 3.2
-KDE 3.0.3 (I'll try it under gnome)
-using .src.rpm versions 4191, 3123, 2960
-Athlon 1700
-1G ram, 6G swap
-64M GF2MX400
Thankyou,
jvf