aMule Forum
English => aMule crashes => Topic started by: macias on September 26, 2006, 09:12:16 PM
-
From time to time (too often really) aMule tries to do something that looks like reorganization of files. Whole system becomes unoperational, HDD works like crazy, mouse cursor cannot be moved, the screen is not refreshed. I have 2GHz CPU but even waiting over an hour to see what will happen does not work.
There was not single time I manage to get the control of the system -- I was forced to hard shutdown the computer.
-
Looks like a files rehash...
-
Actually, it looks like VM exhaustion to me. Macias, make sure you have plenty of free disk space on your swap partition.
-
I don't have swap partition at all. I set it on purpose -- 2GB of RAM should be sufficient enough (not for amule, for every app I work with). When running amule I typically have gdb (for amule), kdevelop, konqueror and konsole loaded.
-
Not to get into an off-topic debate, but please take a look at http://sourcefrog.net/weblog/software/linux-kernel/swap.html
You might find the explanation there.
In short, you will see a lot more disk paging than normal because you've got no swap space. Every single process is residing in your RAM (even processes that haven't been used in a very long time). These would normally be swapped out, to enable all your oft-used processes to use available RAM.
-
Originally posted by VinylPusher
In short, you will see a lot more disk paging than normal because you've got no swap space. Every single process is residing in your RAM (even processes that haven't been used in a very long time). These would normally be swapped out, to enable all your oft-used processes to use available RAM.
Thank you, I understand the general idea, but the result -- no. I cannot agree that 1GB of RAM + 1 GB of swap does something better than just plain 2GB of RAM (put any values you like). Besides I didn't tell I am out of RAM while running aMule and most important -- only aMule kills my HDD. So I guess there are some assumptions in aMule code about swap, memory available, or just not very well optimized algorithm X (X -- because I still don't know what it does).
Now I will try to keep moderate download files number (<100) -- I will see if aMule handles this better.
have a nice day
bye