aMule Forum
English => Multiplatform => Mac OSX => Topic started by: harelj on September 29, 2006, 12:37:25 AM
-
I downloaded amule. I usually use emule with parallels, but for some reason amule will not start.
I have check with consol. the error message is:
===== Thursday, September 28, 2006 3:36:58 PM US/Pacific =====
amule(4170,0xa000ed58) malloc: *** vm_allocate(size=2147487744) failed (error code=3)
amule(4170,0xa000ed58) malloc: *** error: can't allocate region
amule(4170,0xa000ed58) malloc: *** set a breakpoint in szone_error to debug
amule(4170,0xa000ed58) malloc: *** vm_allocate(size=2147487744) failed (error code=3)
amule(4170,0xa000ed58) malloc: *** error: can't allocate region
amule(4170,0xa000ed58) malloc: *** set a breakpoint in szone_error to debug
Usage: amul
Thanks
-
For some reason, it's trying to allocate an unreasonable amount of memory (2GB). I would guess that it's because of a corrupt configuration file.
Try renaming the aMule configuration folder, or moving it temporarily to the Trash. It's located at ~/Library/Application Support/aMule. You should also make sure you have no files or folders with either "amule" or "emule" in the name in ~/Library/Preferences. Now start aMule.
If it still doesn't work, then there's some problem with your system and we'll have to figure that out with more information.
If it does work, then you can use it. If you want to recover files from the aMule configuration folder that you renamed/moved, you can do that. You'll need to quit aMule first. The files cryptkey.dat and preferences.dat are necessary to keep the credits you have earned with clients. And any *.part* files in the Temp directory comprise any partial downloads you had in progress. You might want to move things back in small groups, rather than all at once, so that if the problem comes back you can identify the likely culprit. Of course, keep any *.part* files with the same number together.
-
Finally,
I don't know what the problem was, but it seems as if it works now.
Thanks