Print

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

[m2kio]

hi,

i compiled aMule: <http://little-bat.de/temp/>.

it stalled for me most time, and i've got a clue:

if ip-forwarding in my router is set up to work for aMule, and aMule is about to get a high id from a server, then aMule stalls playing beachball 4ever.

if ip-forwarding is disabled, and aMule only gets a low id, then aMule does not stall.

           ... kio !

fix me fix me fix me fix me fix me fix me fix me fix me fix me

[ken]

Try this.  Run aMule with symbols intact (i.e. not stripped).  When aMule is stalled, issue this command in Terminal:

Code: [Select]

sample amule 1Post the resulting file on your website and put a link to it here.  That way the devs can see what aMule was doing when it stalled.

[m2kio]

ok.

link is <http://little-bat.de/temp/amule_20247.sample.txt>

actually, it's not much, i'll paste it here:

Analysis of sampling pid 20247 every 10.000000 milliseconds
Call graph:
    98 Thread_1d0b
      98 start
        98 _start
          98 main
            98 wxEntry(int&, char**)
              98 wxApp::MainLoop()
                98 wxApp::MacDoOneEvent()
                  98 wxApp::MacHandleOneEvent(void*)
                    98 wxAppConsole::ProcessPendingEvents()
                      98 wxEvtHandler::ProcessPendingEvents()
                        98 wxEvtHandler::ProcessEvent(wxEvent&)
                          98 wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
                            98 wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
                              98 CamuleApp::ListenSocketHandler(wxSocketEvent&)
                                98 CListenSocket::OnAccept(int)
                                  98 wxSocketServer::AcceptWith(wxSocketBase&, bool)
                                    98 GSocket::WaitConnection()
                                      98 GSocket::Input_Timeout()
                                        98 select
                                          98 select
    98 Thread_1e03
      98 _pthread_body
        98 __CFSocketManager
          98 select
            98 select

Total number in stack (recursive counted multiple, when >=5):

Sort by top of stack, same collapsed (when >= 5):
        select        196

[giliii]

I had a similar problem. But then I noticed that the problem maybe wasn’t with the low id high id stuff. I went through testing and conclude that the a problem was with the “Autoconnect on startup” I deactivated and…  amule finally working :d :d :d  :baby:

Try it and see if you still get the same problem !

 

EDIT: You can also get emule stalled when is doing the hashing thing... (saw this one with gdb). After the AICH is terminated emule runs just fine..! (try not to share any directory and the try to connect to see if it get's stalled... other way arround is to open it with gdb and find out when the AICH thread is terminated)

[Kry]

Interesting. Can you confirm that the autoconnect is the one hanging aMule?

[m2kio]

Originally posted by Kry
Interesting. Can you confirm that the autoconnect is the one hanging aMule?

no, at least not for me.

o enabled ip forwarding in router
o started aMule w/o autoconnect@startup
  - aMule did not hang
o waited for AICH to complete
o dbl-clicked on Razorback
  --> Beachball

after 2 minutes connected (at least log printed) responded for some seconds
i got a high id from razorback
i tried to adjust window size (green btn) --> Beachball

after 1/2 minute responding again
working for 1/2 minute (maybe)
stalled again for 10 sec

now for the first time i see uploads! :-)
(now waiting for downloads)

now for the moment it seems to work, no more stalling right now, all upload slots in use.

so maybe after startup with autoconnect it does not lock for ever but just goes to a large amount of connection timeouts for lots of connects

uh, right now all uploads suddenly terminated.
still 2 clients on queue, but both stay in queue?!?
new clients go into queue and advance to upload state.
hangs for a sec or 2 ...
hangs for 5 secs ...
hangs for a sec ...
hangs for 5 secs

note: it seems, that it regularly hangs some secs  when i click on stats window button.

hangs for 5 secs when i collapsed tree view in stats window.
hangs for 30 secs when i clicked on transfer window button. (uploads still there.)

cpu usage is very high... oh, thats safari. all the animated gifs on this page...

amule hangs again. cpu usage 0.0% for about a minute.
lost 4 of 7 upload connections then.

and so on.

     ... kio !

p.s.
note: upload windows says: clients on queue: 1
but when i show the waiting list, there are ~20.
(merde... stalling again... lost all but 1 upload connection...)

[EvoErik]

Dear all!

I've the same problem: Beachball while getting a high id.

Could this be related to a bug in gcc for Mac OS X? Fink reports this:

-------
The version of gcc included with XCode 1.5 is known to produce incorrect output from c++ code under certain circumstances. Fink now has a mechanism to warn users about this, and Fink will soon refuse to use the "broken" gcc to compile packages which are known to have this problem.
-------

Regards,
Erik

[Kry]

Hum.  might be interesting to remove some host resolving on the build and test it... I'll try next days.


I fear a wxWidgets socket problem anyway.

[m2kio]

Originally posted by EvoErik
The version of gcc included with XCode 1.5 is known to produce incorrect output from c++ code under certain circumstances. Fink now has a mechanism to warn users about this, and Fink will soon refuse to use the "broken" gcc to compile packages which are known to have this problem.

no. i have only XCode 1.1 installed. But there are enough bugs in every version of gcc. but it's more that the programs crash in such cases.

there is an option in the amule build options ummary:

 Should aMule be linked against patched gsocket?          no

should i try this patch, and how do i enable it?

           ... kio !

[phoenix]

m2kio,

should i try this patch, and how do i enable it?

For wx-2.4.2: yes.
For wx-2.5.2: yes.
For wx-2.5.3: no.

Actually, IIRC, these are default options, I mean, usually aMule will link with the patched gsocket, unless you are on wx-2.5.3 or greater. There is an option to configure to disable linking with the patched gsocket, --disable-gsocket.

So, probably you are using wx-2.5.3, is that correct? If so, stick to the default.

Cheers!

[m2kio]

Originally posted by phoenix
So, probably you are using wx-2.5.3, is that correct? If so, stick to the default.

yes, i got wx-2.5.3. ok, then the best i can do is wait for rc8.

aMule rc7 on Mac works ... sort of. No comparison to the Intel/Linux experience.

But, keep on working!

            ... kio !

you may put a link to <http://little-bat.de/temp> for the Mac version (OS X 10.3) in the dl area if you like. i'll add a preface to the page.

erm, better <http://little-bat.de/amule>. I'll move it there.

[phoenix]

m2kio,

yes, i got wx-2.5.3. ok, then the best i can do is wait for rc8.

Sorry, but I disagree. If you just wait for rc8, you will get the same problem in rc8. We must fix that.

I did not understand what you mean by playing beachball ?(. I also experience some periodic hangs from aMule, but not particularly on connecting, it's every time, but they are usually 3-4 second hangs. Is that what you mean? Btw, I always have a high id, but i can test on a low id machine too.

Cheers!

[m2kio]

Originally posted by phoenix
I did not understand what you mean by playing beachball ?(. I also experience some periodic hangs from aMule, but not particularly on connecting, it's every time, but they are usually 3-4 second hangs. Is that what you mean? Btw, I always have a high id, but i can test on a low id machine too.

beachball: the busy cursor. shown when the OS has an event to deliver but isn't polled. (that's how i imagine it works). Thus: you don't see it hanging, in first place. you only see that it's hanging if you require amule to respond to a mouse click or movement. then it takes a sec or 2 and then the mouse pointer is set to a beach ball by the OS.

summary of my current state:
- it works. sort of.
- i get a high id.
- upload and download work. wacky.
- it frequently, sometimes regularly (~1 minute) hangs for some seconds to a minute or so.
  meanwhile cpu usage 0.0% and "sample amule 1" always looks similar: <http://little-bat.de/temp/amule_20247.sample.txt>
- on connect to a server it hangs for up to a minute or so. (right now: razorback only 5 secs)
- if starting with auto connect to server, it hangs quite a while. (i now have disabled autoconnect)
  or it hangs until it crashes (right now on my ibook)
- it frequently crashes on user action. (GUI issue?)
- console sometimes reports bogus mfrees.
  e.g.: *** malloc[352]: Deallocation of a pointer not malloced: 0xd3712cb; 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
- quite a lot GUI drawing quirks.

i'm willing to support debugging. but i might need help.  :]

      ... kio !

[lionel77]

Here's another observation: Whether amule freezes upon server connect or not seems to be highly determined by the actual server you are trying to connect to.

For instance, trying to connect to most of the "big"-servers (e.g. razorback 2, donkey server no 4, byte devils, etc.) reliably freezes my amule.

In contrast, when I try to connect to lionet (212.199.125.36:8080) or "###doingdo####" (205.209.136.190:4661) amule never freezes.


So maybe it's one of the "advanced" lugdunum features (eg zlib compression?) that is causing amule to choke...

[Kry]

Can you disable UDP socket and test?