aMule Forum
English => en_Bugs => Topic started by: Master on April 13, 2004, 05:48:08 PM
-
HI,
It seems to me that amule 2.0.0_rc2 does not check for available space before it starts downloading a file. Today, I got a message about not being able to write on the hdd because there was no space available. If I remember correctly amule 2.0.0_rc1 was checking for the available space and it was making sure that there is enough space to accommodate the files I am downloading.
-
take a look at prefs -> file ;)
greets
-
Check disk space was enabled, but it was set to 1MB.
Thanks deltaHF
-
ur welcome :)
i had last time 24 kb free on my hdd.. ;)
-
There has to be a bug ....
I have enabled the check space option and I have set the limit to 200MB. However I got the following error
EMule error
can't write to file descriptor 23 (error 28:No space left on device)
The other interesting thing is that only 50MB are available on the hdd.
It seems to me or better say I am sure that aMule is ignoring my settings.
Of course now that I am getting the error, amule is very unresponsive.
-
When I was getting this error I was downloading a file with 20KB/s now that I paused it, it does not complain.
-
This is weird!
The free space of the hdd is decreasing! I thought that amule was allocating the necessary space for the file at the begining of the download process. Has that changed?
-
One last thing...
When I closed amule I saw the following disturbing message:
aMule dialog destroyed
free(): invalid pointer 0x860e608!
Now, exiting main app...
-
Originally posted by Master
One last thing...
When I closed amule I saw the following disturbing message:
aMule dialog destroyed
free(): invalid pointer 0x860e608!
Now, exiting main app...
fixed ;)
-
About the free() invalid pointer... it's a known bug (take a look at http://www.amule-project.net/amule/thread.php?threadid=1666&sid= ) and will be fixed in rc3. Maybe all other problems where due to this one? Who knows :-P Wierd, indeed.
Thanks for the reports.
Regards!