Print

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

[alphonsetram]

Amule was working very well since months...
last week I had a download during like 36hours.
and when I tried to open amule it was in the dock but I couldn't open it...
I waited and nothing happened so I had to kill the application
Since that time , amule didn't work anymore.
It stays frozen at start with the multicolor circle...i waited like 20 minutes but nothing happens.

So I made a backup of my temp files...delete the application and tried to download it again and reinstall it.

and now i can't have access to the "preferences settings window" I waited 30 minutes but I only had the colored circle.

After a few researches in the forum, I deleted the app again, the folder amule in /user/library/application support/ the .org file in /user/library/preferences .... and all amule reference found in spotlight.

SAME PROBLEM

I did it again with a new user created in /system preference/account ....

SAME PROBLEM

I did it again with the CSV version , I married the mule ....

SAME PROBLEM so I'm thinking about a divorce now...

I can't have access to the preference window anymore and I don't know what to do next.....

Here is the terminal window I had with the CSV version...

External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
Empty dir /Users/stan/Documents/aMule Downloads/ shared
HTTP download thread started
Host: ocbmaurice.dyns.net:80
URL: http://ocbmaurice.dyns.net/pl/slist.pl?download/server-best.met
Response: 0 (Error: 3)
WARNING: Void response on stream creation
HTTP download thread ended
amule(737,0x213a800) malloc: ***  Deallocation of a pointer not malloced: 0xf0212754; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug

[lionel77]

Could you try creating a dummy user account and running aMule from there? (see here for more details)

[Kry]

lio, explain how to disable server-met auto-update on startup.

[lionel77]

Originally posted by Kry
lio, explain how to disable server-met auto-update on startup.

When he deletes/renames '~/Library/Application Support/aMule" he effectively does this, because then a new amule.conf file is created and 'server-met auto-update on startup' is not enabled by default.

EDIT:
alphonsetram, if you could just quickly try the dummy account thing I mentioned above, we would be able to narrow down the cause of your problems.

[alphonsetram]

Like I said in my first message...

I did it again with a new user created in /system preference/account ....

SAME PROBLEM


I allready tried that...

[lionel77]

Sorry, I must have overlooked that you had already tried running aMule from a clean new user account.

Wow, that's really extra wild, I'd say. By running aMule from the new user account you ensure that none of the original config files are used, so even if those got borked somehow, that would not matter.

Could you try running my latest CVS version again from the clean user account and then paste the Terminal output here? And just to be clear, switching to the other windows etc. works fine, right? It's only opening the preference window that gives you the beachball of death, right?

[alphonsetram]

I know it's weird....
For the CSV in dummy mode..I have the same message I gave you in the first Post in the Terminal

"amule(737,0x213a800) malloc: *** Deallocation of a pointer not malloced: 0xf0212754; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug"

and after nothing during 20 mins so I did a Ctrl-alt-esc, Amule is in (not responding) mode
and terminal said "killed" that's all.

And yes it's only with the preference panel that I have the beachball of death but I need it to change ports etc etc...before doing anything else...

I have the first amule.crash.log from the famous INITIAL crash .The beginning of all the problem if you want to have a look...

==================================
==================================
Host Name:      HAL
Date/Time:      2006-08-23 22:17:21.713 +0200
OS Version:     10.4.7 (Build 8J135)
Report Version: 4

Command: amule
Path:    /Applications/P2P/aMule.app/Contents/MacOS/amule
Parent:  WindowServer [55]

Version: 2.1.2 (2.1.2)

PID:    251
Thread: 0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000224

Thread 0 Crashed:
0   org.amule.aMule                   0x00090258 CamuleDlg::AddServerMessageLine(wxString&) + 28 (crt.c:355)
1   <<00000000>>    0xbffff714 0 + -1073744108
2   org.amule.aMule                   0x0008da54 CamuleGuiApp::AddServerMessageLine(wxString&) + 32 (crt.c:355)
3   org.amule.aMule                   0x00069920 CServerSocket::ProcessPacket(char const*, unsigned, unsigned char) + 3820 (crt.c:355)
4   org.amule.aMule                   0x0006b564 CServerSocket::PacketReceived(CPacket*) + 108 (crt.c:355)
5   org.amule.aMule                   0x0003cc8c CEMSocket::OnReceive(int) + 804 (crt.c:355)
6   org.amule.aMule                   0x000677a0 CServerSocket::OnReceive(wxSocketError) + 80 (crt.c:355)
7   org.amule.aMule                   0x0015dd2c wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) + 180 (crt.c:355)
8   org.amule.aMule                   0x0015df94 wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) + 156 (crt.c:355)
9   org.amule.aMule                   0x0015e158 wxEvtHandler::ProcessEvent(wxEvent&) + 212 (crt.c:355)
10  org.amule.aMule                   0x0015e4b8 wxEvtHandler::ProcessPendingEvents() + 116 (crt.c:355)
11  org.amule.aMule                   0x0016ada4 wxAppConsole::ProcessPendingEvents() + 124 (crt.c:355)
12  org.amule.aMule                   0x0019b57c wxApp::MacHandleOneEvent(void*) + 84 (crt.c:355)
13  org.amule.aMule                   0x0019b640 wxApp::MacDoOneEvent() + 176 (crt.c:355)
14  org.amule.aMule                   0x003330f0 wxEventLoop::Dispatch() + 52 (crt.c:355)
15  org.amule.aMule                   0x0032c4e0 wxEventLoopManual::Run() + 224 (crt.c:355)
16  org.amule.aMule                   0x001a1780 wxAppBase::MainLoop() + 108 (crt.c:355)
17  org.amule.aMule                   0x0025b4cc wxEntry(int&, wchar_t**) + 144 (crt.c:355)
18  org.amule.aMule                   0x0008d7ac main + 24 (crt.c:355)
19  org.amule.aMule                   0x000020cc _start + 340 (crt.c:272)
20  org.amule.aMule                   0x00001f74 start + 60

Thread 1:
0   libSystem.B.dylib                 0x9001f7ac select + 12
1   com.apple.CoreFoundation          0x907ee40c __CFSocketManager + 472
2   libSystem.B.dylib                 0x9002bc28 _pthread_body + 96


etc etc ...I attached the full log.

[ken]

Host Name: HAL

There's your problem.  Your computer is psychotic.  

But seriously, things you might try:

• When aMule is frozen (showing the spinning beachball), use Activity Monitor to sample it.  In Activity Monitor, double-click on the amule process.  In the resulting dialog, press the Sample button.  Save the sample and attach it to a reply here.
• Trash your ~/Library/Application Support/aMule folder (as you have done before), start aMule but then immediately quit it.  You should then have a new settings folder with a fresh amule.conf file.  You can edit that file to change your settings instead of using the preferences dialog.  It's tedious, but it will work.
• Make sure you aren't running anything based on the BOINC framework (e.g. Seti@HOME) or the distributed.net client.  These are known to interact badly with aMule.  We don't really know why.

[alphonsetram]

So I made a sample like you asked when Amule is in "psychotic' mode. (Sample1)

By the way I'm not running anything beside amule...I start the computer , launch amule and same problem.
and I precise that I have no soft in automatic launch on startup.

After I tried to edit amule.conf file and It worked so I was able to connect the network so I tried to download something...but when I tried to "Right click" the file in the transfer panel to change the priority on HIGH , I had the spinning beachball...and before I saw display problems on the network list and the upload list...
like some lines were effective but I couldn't see them (underlined but nothing written) so I restarted and same problem...weird things in the server list..a little froze during 2 mins and after a big froze when I trieed to "right click" the download file. So I made a sample of that too... (Sample2)

thanks for your time

[alphonsetram]

and the second sample

[ken]

The first sample seems to show a problem initializing the locale.  I don't know if it's a bug in wxWidgets or in aMule.  Try this: quit aMule, edit the amule.conf file, set Language=en_US, start aMule, open the Preferences dialog.  Does it still hang?

The second problem is the one that lionel77 has been struggling with for so long.  One part of aMule is adding tasks to a queue.  Another part of aMule is supposed to take a task off the queue and perform it, and then go back to the task queue and get another.  If there isn't one available yet, it can tend to other business, like responding to your clicks.  The problem is that the part performing tasks is taking too long; it's just too slow.  It can't keep up with the part that's adding tasks to the queue.  So, there are more and more tasks on the queue -- it's never getting smaller, let alone empty.  So, this part of aMule can never get around to responding to your clicks.

The only solution is to reduce the amount of work that aMule is trying to do.  Share fewer files.  Download fewer files.  Reduce your maximum sources per file and maximum connections.  Maybe disable the Kademlia (Kad) network.

[jeroip]

Just to let you know: I'm having the exact same problem. I started having some performance problems with aMule (like with all P2P apps for Mac OS X I have tried so far...) so I decided to trash the app and reinstall it with a brand new version. I deleted everything, App Support files, prefs, the works. I downloaded 2.1.3, installed it, clicked the Preferences button to customize the default settings and voila: endless spinning beach ball. Did the whole procedure once more, same results.

I got so annoyed I threw away aMule all together, and tried some other P2P apps out of sheer frustration, but when I tried others (Poisoned, Acqlite, Edonkey2000 and the likes) I was once again reminded of the fact that aMule sucks the least, so I want it back!  

I'm going to try rolling back to 2.1.2, maybe that'll work...?

[jeroip]

Rolling back to 2.1.2 or 2.1.1 didn't work. In fact, as a result I am now unable to even start the app. On startup I get the beachball immediately. Which makes me suspicious of the installation procedure of aMule. Are any files placed in directories where a Mac GUI application normally shouldn't, such as /usr/bin? Because that would explain that I can't use previous versions of aMule, even after trashing every file I can find that has something to do with the app. Could somebody help me with this?

[lionel77]

jerop:

To clean aMule from your system you need to remove the following things:
- the aMule application
- the amule settings folder "~/Library/Application Support/aMule" (the ~ here represents your home folder)
- the file "com.amule.plist" in "~/Library/Preferences" (if it exists).

That's all. There is nothing installed in folders such as /usr, /etc and the like.

Btw, what kind of Mac do you have (cpu + ram) and which version of OS X are you running?

[jeroip]

Thanks for your reply, lionel77. My Mac is a G4 PPC, 1.25 GHz, 512MB Ram, OS X 10.3.9.

I've got it working again, with the latest CVS build, starting it from Terminal with the marry-flag. At first that didn't work either. It hung on startup. Only after editing the config-file twice manually (so that the app didn't connect to ED2K and Kad automatically, and after that changing those settings back to default) it worked. But I'm still wondering why I can't install an older version of the software, even after removing all the files that aMule installs. Could it be that some preferences are cached by the Mac OS X Java engine, and cause a conflict? And that by editing the config I forced the engine to reload the config files in its cache?

The latest CVS build works like a dream, by the way!