Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[maxl]

Hi,

I can't get aMule started on Mac OS X Tiger. When I click the icon in the Dock, it just bounces once and doesn't start. Here's what's appears in my user's console.log:

Code: [Select]

amule(1437,0xa000d000) malloc: *** vm_allocate(size=2147487744) failed (error code=3)
amule(1437,0xa000d000) malloc: *** error: can't allocate region
amule(1437,0xa000d000) malloc: *** set a breakpoint in szone_error to debug
amule(1437,0xa000d000) malloc: *** vm_allocate(size=2147487744) failed (error code=3)
amule(1437,0xa000d000) malloc: *** error: can't allocate region
amule(1437,0xa000d000) malloc: *** set a breakpoint in szone_error to debug
Usage: amul

It's strange since aMule has worked just fine before, and I can't recall that I've done anything extraordinary lately.

But what's even stranger is that when I launch aMule from terminal without any parameters it starts up without problems. But when I run it with some parameters e.g. amule --help, it crashes with the same output as above:

Code: [Select]

$ /Applications/aMule.app/Contents/MacOS/amule --help
amule(1496,0xa000d000) malloc: *** vm_allocate(size=2147487744) failed (error code=3)
amule(1496,0xa000d000) malloc: *** error: can't allocate region
amule(1496,0xa000d000) malloc: *** set a breakpoint in szone_error to debug
amule(1496,0xa000d000) malloc: *** vm_allocate(size=2147487744) failed (error code=3)
amule(1496,0xa000d000) malloc: *** error: can't allocate region
amule(1496,0xa000d000) malloc: *** set a breakpoint in szone_error to debug
Usage: amul

I'm running Mac OS X 10.4.10 with aMule 2.1.3 binary downloaded from amule.org.

(There are two threads [1, 2] on this forum, which describe the same problem, but the solutions didn't work for me )


Thanks for any help!

[scalimani]

A friend of mine had the same problem (aMule 2.1.3 not starting) but I don't remember the output on console! We found out that aMule didn't start just on his user, and we didn't understand why! We tried to delete amule folder in application support but nothing changed, so he had to create a new account and move all his data. Try to open aMule in another account and let me know if it works...

[qtip]

I had a similiar problem but never seemed to be able to resolve to a stable solution. I later found the CVS build and started to run that thru terminal and things improved dramatically. Its a bit of a pain to launch as you need to load thru terminal, but its well worth it in forms of stability. See above sticky'd thread for more info in the Mac OSX forum.

hope this helps