aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: TIGER, Crashes 30 minutesafter launch  (Read 6383 times)

tiger_pers

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
TIGER, Crashes 30 minutesafter launch
« on: July 13, 2005, 05:57:21 PM »
Hi,

When I launch my amule 2.0.3 (I tried all older versions) my amule freeze around 30 minutes to 1 hour after the launch.
The amule.app si blocked and I have to kill the application and relaunch.

Any idea of my problem ?
Thanks a lot in advance.

Regards
« Last Edit: July 13, 2005, 05:57:50 PM by tiger_pers »
Logged
Imac G5, 1,8GHZ, 20"

snac

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 34
Re: TIGER, Crashes 30 minutesafter launch
« Reply #1 on: July 14, 2005, 08:17:38 PM »
1) Update at 10.4.2
2) Reinstall Amule
3) Backup credit e key and delete .aMule directory
4) You control doors if opened on Firewall in Network Settings.

Good Luck. :)
Logged
Desktop:: AMD Barton 2600 + ArchLinux Heavy Modded + KDE 3.4.1 + aMule 2.0.3
Portable:: Ibook G4 - 1,25Ghz - OSX 10.3.9
Linux User Nr.372724

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: TIGER, Crashes 30 minutesafter launch
« Reply #2 on: July 15, 2005, 09:27:41 AM »
Hi tiger_pers,

What I'd like you to do is run aMule 2.0.3 until it hangs.  Do not Force Quit it, yet.

Instead, please do the following:

  • Run the Terminal program.  You will find it in /Applications/Utilities.
  • In Terminal, type the following command: sample amule 10

That command will output some text, including a line that looks like this: Sample analysis of process XXX written to file /tmp/amule_XXX.sample.txt
  • Now you can Force Quit aMule and, if you like, restart it.
  • In terminal, type the command: mv /tmp/amule_XXX.sample.txt ~/Desktop

Use the proper value that was output from the "sample" command instead of "XXX".
  • Reply to this thread and attach that .sample.txt file to your posting.

Hopefully, the information in that file will allow me to figure out what is going wrong with your aMule.  Thanks for your help.  :)
Logged

tiger_pers

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
Re: TIGER, Crashes 30 minutesafter launch
« Reply #3 on: July 17, 2005, 05:21:06 PM »
Hi,

My TIGER is now in 10,4,2 and you will find the content of my "Exited process_244.sample.txt" file :
------------------
Analysis of sampling pid 244 every 10.000000 milliseconds
Call graph:
    905 Thread_0f3f
      905 0x28bc
        905 0x2a48
          905 0x11f1c
            905 0x15021e4
              905 0x10cca60
                905 0x10ccdfc
                  905 0x93228740
                    905 0x931231ec
                      905 0x93123be0
                        905 0x9074acdc
                          905 0x9074b728
                            905 0x9075edb0
                              905 0x1197674
                                905 0x15426a8
                                  905 0x1541c7c
                                    905 0x15424fc
                                      905 0xf68c
                                        905 0x53bac
                                          905 0x10b24c
                                            905 0x20068
                                              905 0x1283d4
                                                905 0x149c8d8
                                                  905 0x9001bc60
                                                    905 0x9001bc60
    905 Thread_1003
      905 0x9002c3d4
        905 0x9001efec
          905 0x9001efec

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

Sort by top of stack, same collapsed (when >= 5):
        0x9001bc60        905
        0x9001efec        905
------------------

Thanks for your help.
Regards
Logged
Imac G5, 1,8GHZ, 20"

tiger_pers

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
Re: TIGER, Crashes 30 minutesafter launch
« Reply #4 on: July 17, 2005, 10:13:29 PM »
Sorry, now it's the right file "amule_326.sample.txt" :
Code: [Select]
Analysis of sampling pid 326 every 10.000000 milliseconds
Call graph:
    949 Thread_0f1b
      949 0x28bc
        949 0x2a48
          949 0x11f1c
            949 wxEntry(int&, wchar_t**)
              949 wxApp::MainLoop()
                949 wxApp::MacDoOneEvent()
                  949 ReceiveNextEventInMode
                    949 ReceiveNextEventCommon
                      949 RunCurrentEventLoopInMode
                        949 CFRunLoopRunSpecific
                          949 __CFRunLoopRun
                            949 __CFRunLoopDoTimer
                              949 wxTimerBase::Notify()
                                949 wxEvtHandler::ProcessEvent(wxEvent&)
                                  949 wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
                                    949 wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
                                      949 0xf68c
                                        949 0x53bac
                                          949 0x10b24c
                                            949 0x20068
                                              949 0x1283d4
                                                949 wxSocketClient::Connect(wxSockAddress&, bool)
                                                  949 GSocket::Connect(GSocketStream)
                                                    949 connect
                                                      949 connect
    949 Thread_1003
      949 _pthread_body
        949 __CFSocketManager
          949 select
            949 select

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

Sort by top of stack, same collapsed (when >= 5):
        connect        949
        select        949
Thanks for your help
Regards

[Edited to use code tags -- ken]
« Last Edit: July 17, 2005, 11:44:22 PM by tiger_pers »
Logged
Imac G5, 1,8GHZ, 20"

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: TIGER, Crashes 30 minutesafter launch
« Reply #5 on: July 18, 2005, 12:52:31 AM »
OK.  I don't know what's going on there.  You seem to be blocking in a call to connect(), but I'm almost certain that the socket was set to be non-blocking.  Weird.

What is your Max. Connections set to?  How many items in your Downloads list?
Logged

tiger_pers

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
Re: TIGER, Crashes 30 minutesafter launch
« Reply #6 on: July 18, 2005, 10:34:11 PM »
Hi,

I have deleted .amule directory and re-install amule.
But I have still the problem, you will find here the new amule_372.sample.txt file.

My config :
* Connections
  - Bandwith Limits (Down 600 / Up 100 / Slot Allocation 10)
  - Line Capacities (Down 300 / Up 30
  - Max Sources per file (Hard 300 / Max Connections 500)
* Core tweaks
   - Max new connections / 5 secs : 20
Quote
--------------------
Analysis of sampling pid 372 every 10.000000 milliseconds
Call graph:
    953 Thread_0f43
      953 0x28bc
        953 0x2a48
          953 0x11f1c
            953 wxEntry(int&, wchar_t**)
              953 wxApp::MainLoop()
                953 wxApp::MacDoOneEvent()
                  953 ReceiveNextEventInMode
                    953 ReceiveNextEventCommon
                      953 RunCurrentEventLoopInMode
                        953 CFRunLoopRunSpecific
                          953 __CFRunLoopRun
                            953 __CFRunLoopDoTimer
                              953 wxTimerBase::Notify()
                                953 wxEvtHandler::ProcessEvent(wxEvent&)
                                  953 wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
                                    953 wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
                                      953 0xf68c
                                        953 0x53bac
                                          953 0x10b24c
                                            953 0x20068
                                              953 0x1283d4
                                                953 wxSocketClient::Connect(wxSockAddress&, bool)
                                                  953 GSocket::Connect(GSocketStream)
                                                    953 connect
                                                      953 connect
    953 Thread_1003
      953 _pthread_body
        953 __CFSocketManager
          953 select
            953 select

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

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

Analysis of sampling pid 372 every 10.000000 milliseconds
Call graph:
    953 Thread_0f43
      953 0x28bc
        953 0x2a48
          953 0x11f1c
            953 wxEntry(int&, wchar_t**)
              953 wxApp::MainLoop()
                953 wxApp::MacDoOneEvent()
                  953 ReceiveNextEventInMode
                    953 ReceiveNextEventCommon
                      953 RunCurrentEventLoopInMode
                        953 CFRunLoopRunSpecific
                          953 __CFRunLoopRun
                            953 __CFRunLoopDoTimer
                              953 wxTimerBase::Notify()
                                953 wxEvtHandler::ProcessEvent(wxEvent&)
                                  953 wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
                                    953 wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
                                      953 0xf68c
                                        953 0x53bac
                                          953 0x10b24c
                                            953 0x20068
                                              953 0x1283d4
                                                953 wxSocketClient::Connect(wxSockAddress&, bool)
                                                  953 GSocket::Connect(GSocketStream)
                                                    953 connect
                                                      953 connect
    953 Thread_1003
      953 _pthread_body
        953 __CFSocketManager
          953 select
            953 select

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

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

-----------------------

Thanks for your help,
Regards,
« Last Edit: July 18, 2005, 10:37:31 PM by tiger_pers »
Logged
Imac G5, 1,8GHZ, 20"

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: TIGER, Crashes 30 minutesafter launch
« Reply #7 on: July 19, 2005, 04:23:38 AM »
Well, at least it's consistent.  Are you running another network-intensive program at the same time as aMule?

Here's another command to get more information.  At a time when aMule is frozen, type this in the Terminal: netstat -anp tcp
Please post the output from that.

Also, you didn't say how many files are in your Downloads list.
Logged

tiger_pers

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
Re: TIGER, Crashes 30 minutesafter launch
« Reply #8 on: July 19, 2005, 02:04:59 PM »
Ok, I will send the command at the end of this afternoon.
I have 12 items in my download list.
Regards
Logged
Imac G5, 1,8GHZ, 20"

tiger_pers

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
Re: TIGER, Crashes 30 minutesafter launch
« Reply #9 on: July 19, 2005, 10:19:10 PM »
Hi, here the result of the sample:
Quote
Analysis of sampling pid 193 every 10.000000 milliseconds
Call graph:
    943 Thread_0f4f
      943 0x28bc
        943 0x2a48
          943 0x11f1c
            943 wxEntry(int&, wchar_t**)
              943 wxApp::MainLoop()
                943 wxApp::MacDoOneEvent()
                  943 ReceiveNextEventInMode
                    943 ReceiveNextEventCommon
                      943 RunCurrentEventLoopInMode
                        943 CFRunLoopRunSpecific
                          943 __CFRunLoopRun
                            943 __CFRunLoopDoTimer
                              943 wxTimerBase::Notify()
                                943 wxEvtHandler::ProcessEvent(wxEvent&)
                                  943 wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
                                    943 wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
                                      943 0xf68c
                                        943 0x53bac
                                          943 0x10b24c
                                            943 0x20068
                                              943 0x1283d4
                                                943 wxSocketClient::Connect(wxSockAddress&, bool)
                                                  943 GSocket::Connect(GSocketStream)
                                                    943 connect
                                                      943 connect
    943 Thread_1003
      943 _pthread_body
        943 __CFSocketManager
          943 select
            943 select

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

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

Here the result oft the netstat command:
Quote
Active Internet connections (including servers)
Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)
tcp4       0      0  *.3689                 *.*                    LISTEN
tcp4       0      0  *.*                    *.*                    CLOSED
tcp4       0      0  192.168.1.101.50903    81.60.103.117.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50902    217.132.43.138.4662    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50901    201.239.122.100.8348   CLOSE_WAIT
tcp4       0      0  192.168.1.101.50900    80.172.153.40.45800    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50899    84.99.205.16.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50898    82.52.112.74.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50896    196.206.160.241.4662   CLOSE_WAIT
tcp4       0      0  192.168.1.101.50895    84.94.137.13.24363     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50894    83.25.148.112.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50893    82.50.126.231.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50892    83.29.97.200.31229     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50891    80.36.165.98.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50890    81.155.13.77.4275      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50889    194.184.19.98.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50888    83.44.184.140.10493    CLOSE_WAIT
tcp4      66      0  192.168.1.101.50887    83.43.83.217.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50886    81.202.249.241.80      CLOSE_WAIT
tcp4      85      0  192.168.1.101.50885    85.53.68.205.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50884    83.43.209.151.4662     CLOSE_WAIT
tcp4      18      0  192.168.1.101.50883    81.34.226.95.8665      CLOSE_WAIT
tcp4      18      0  192.168.1.101.50882    81.34.114.1.4662       CLOSE_WAIT
tcp4      90      0  192.168.1.101.50881    200.55.94.153.19455    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50880    213.98.213.31.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50878    213.103.63.2.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50877    80.38.201.124.4662     CLOSE_WAIT
tcp4      85      0  192.168.1.101.50876    82.254.227.54.4662     CLOSE_WAIT
tcp4      85      0  192.168.1.101.50875    85.49.64.203.20        CLOSE_WAIT
tcp4       0      0  192.168.1.101.50874    83.157.129.94.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50873    83.37.65.99.4662       CLOSE_WAIT
tcp4       0      0  192.168.1.101.50872    83.202.172.6.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50871    82.120.5.244.4662      CLOSE_WAIT
tcp4      85      0  192.168.1.101.50870    212.79.152.107.1662    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50869    81.36.207.2.4662       CLOSE_WAIT
tcp4       0      0  192.168.1.101.50868    83.50.75.200.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50867    85.50.4.230.4662       CLOSE_WAIT
tcp4       0      0  192.168.1.101.50866    200.81.225.32.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50865    83.41.32.48.4662       CLOSE_WAIT
tcp4       0      0  192.168.1.101.50864    212.97.187.30.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50863    80.224.101.38.4662     CLOSE_WAIT
tcp4      85      0  192.168.1.101.50862    84.120.213.98.4662     CLOSE_WAIT
tcp4      85      0  192.168.1.101.50861    81.38.147.147.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50860    82.212.181.240.4662    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50859    85.48.130.212.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50858    83.44.235.4.6881       CLOSE_WAIT
tcp4       0      0  192.168.1.101.50857    83.43.118.165.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50856    82.254.19.166.2468     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50855    82.52.149.181.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50854    80.32.66.40.4662       CLOSE_WAIT
tcp4       0      0  192.168.1.101.50853    82.185.46.83.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50851    151.37.27.160.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50850    201.8.2.75.4662        CLOSE_WAIT
tcp4       0      0  192.168.1.101.50849    81.202.197.109.26496   CLOSE_WAIT
tcp4     119      0  192.168.1.101.50848    217.132.67.207.6662    CLOSE_WAIT
tcp4     138      0  192.168.1.101.50847    201.224.104.175.4662   CLOSE_WAIT
tcp4       0      0  192.168.1.101.50846    200.146.125.120.4662   CLOSE_WAIT
tcp4       0      0  192.168.1.101.50845    85.49.71.89.29318      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50844    213.60.52.176.1547     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50843    82.56.118.61.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50842    82.54.163.2.4662       CLOSE_WAIT
tcp4       0      0  192.168.1.101.50839    195.36.141.224.4662    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50838    213.103.212.142.4662   CLOSE_WAIT
tcp4       0      0  192.168.1.101.50837    62.147.208.17.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50836    80.132.110.53.22       CLOSE_WAIT
tcp4       0      0  192.168.1.101.50835    200.175.229.108.4662   CLOSE_WAIT
tcp4       0      0  192.168.1.101.50834    85.101.194.212.4662    CLOSE_WAIT
tcp4     138      0  192.168.1.101.50832    219.95.200.134.4662    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50831    81.38.28.104.12121     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50829    220.123.251.252.4703   CLOSE_WAIT
tcp4       0      0  192.168.1.101.50828    151.46.7.42.4662       CLOSE_WAIT
tcp4       0      0  192.168.1.101.50827    84.122.195.69.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50826    200.161.186.151.4662   CLOSE_WAIT
tcp4       0      0  192.168.1.101.50825    83.113.12.7.5662       CLOSE_WAIT
tcp4       0      0  192.168.1.101.50824    82.48.253.88.7333      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50823    83.45.114.72.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50822    83.36.37.76.8888       CLOSE_WAIT
tcp4       0      0  192.168.1.101.50821    83.53.225.144.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50820    218.168.157.144.4662   CLOSE_WAIT
tcp4       0      0  192.168.1.101.50819    81.184.38.70.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50818    84.59.212.217.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50817    217.129.29.204.4662    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50816    83.45.19.74.4662       CLOSE_WAIT
tcp4       0      0  192.168.1.101.50815    82.66.55.200.36328     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50814    62.147.168.122.4672    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50813    68.206.55.254.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50810    222.100.39.188.4662    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50809    193.95.219.27.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50808    82.52.146.123.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50807    84.56.138.110.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50806    195.78.12.155.9505     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50805    81.32.141.204.4001     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50804    83.52.251.145.4662     CLOSE_WAIT
tcp4      85      0  192.168.1.101.50803    213.98.37.175.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50802    82.235.78.214.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50800    81.57.122.128.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50799    82.254.78.212.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50798    81.44.63.168.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50796    83.194.157.158.4661    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50794    85.137.55.149.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50793    82.126.223.24.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50791    83.34.3.224.4662       CLOSE_WAIT
tcp4       0      0  192.168.1.101.50789    83.33.195.103.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50788    83.33.150.221.4662     CLOSE_WAIT
tcp4      18      0  192.168.1.101.50786    218.164.100.90.4662    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50785    85.96.129.226.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50784    80.103.191.4.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50783    85.54.244.244.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50782    62.15.115.171.6732     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50781    81.42.218.205.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50780    82.159.114.82.8091     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50779    61.228.78.102.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50778    62.42.111.13.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50777    81.214.236.144.4662    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50776    193.95.238.12.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50775    80.171.8.167.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50774    62.99.80.184.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50773    82.66.158.52.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50772    82.130.240.72.80       CLOSE_WAIT
tcp4       0      0  192.168.1.101.50771    80.39.16.193.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50770    84.102.175.21.10024    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50769    84.101.45.185.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50767    81.202.214.71.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50766    68.206.207.121.4662    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50765    201.8.238.161.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50764    83.68.65.71.4662       CLOSE_WAIT
tcp4       0      0  192.168.1.101.50763    81.37.233.143.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50762    80.180.126.164.4663    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50761    172.187.169.9.4662     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50751    81.44.59.133.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50747    81.34.150.55.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50744    218.147.179.110.4662   CLOSE_WAIT
tcp4       0      0  192.168.1.101.50743    84.90.57.180.4662      CLOSE_WAIT
tcp4       0      0  192.168.1.101.50736    201.141.41.207.4662    CLOSE_WAIT
tcp4       0      0  192.168.1.101.50711    81.172.25.8.466        CLOSE_WAIT
tcp4       0      0  192.168.1.101.50709    83.39.175.178.4662     CLOSE_WAIT
tcp4   33120      0  192.168.1.101.50528    220.94.134.209.4662    ESTABLISHED
tcp4    7814      0  192.168.1.101.50374    82.121.201.60.6346     CLOSE_WAIT
tcp4       0      0  192.168.1.101.50295    80.35.36.44.4662       CLOSE_WAIT
tcp4       0      0  192.168.1.101.49824    83.135.130.237.4662    CLOSE_WAIT
tcp4       0      0  192.168.1.101.49722    83.201.121.3.4662      CLOSE_WAIT
tcp4      46      0  192.168.1.101.49513    81.57.22.13.7662       CLOSE_WAIT
tcp4      52      0  192.168.1.101.49453    140.122.238.86.4662    CLOSE_WAIT
tcp4       0      0  192.168.1.101.49293    84.144.112.158.4662    CLOSE_WAIT
tcp4       0      0  192.168.1.101.65406    80.129.213.120.4662    CLOSE_WAIT
tcp4      79      0  192.168.1.101.65305    84.170.195.160.4662    CLOSE_WAIT
tcp4   33792      0  192.168.1.101.63697    83.30.213.45.4662      ESTABLISHED
tcp4     476      0  192.168.1.101.49264    195.245.244.243.4661   ESTABLISHED
tcp4       0      0  127.0.0.1.1033         127.0.0.1.1015         ESTABLISHED
tcp4       0      0  127.0.0.1.1015         127.0.0.1.1033         ESTABLISHED
tcp4       0      0  *.9002                 *.*                    LISTEN
tcp4       0      0  *.21227                *.*                    LISTEN
tcp4       0      0  *.9502                 *.*                    LISTEN
tcp4       0      0  *.*                    *.*                    CLOSED
tcp4       0      0  127.0.0.1.1033         127.0.0.1.1017         ESTABLISHED
tcp4       0      0  127.0.0.1.1017         127.0.0.1.1033         ESTABLISHED
tcp4       0      0  *.631                  *.*                    LISTEN
tcp4       0      0  127.0.0.1.1033         127.0.0.1.1019         ESTABLISHED
tcp4       0      0  127.0.0.1.1019         127.0.0.1.1033         ESTABLISHED
tcp4       0      0  127.0.0.1.1033         *.*                    LISTEN
tcp4       0      0  *.515                  *.*                    LISTEN
tcp6       0      0  *.515                  *.*                    LISTEN

Thanks for your help,
regards
Logged
Imac G5, 1,8GHZ, 20"

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: TIGER, Crashes 30 minutesafter launch
« Reply #10 on: July 22, 2005, 06:22:44 AM »
I don't understand what's going on.

I've double-checked the wxMac code and it shouldn't be possible for the process to get stuck in the call to connect.  The socket is set to be non-blocking.

Also, nobody else on Tiger is having this problem.

So, I suspect that it is something about your system.  Do you have any special network-related software installed?  Any kernel extensions or network monitoring or security software?  Are you running other p2p software?

What happens if you create a new user account and run aMule from there instead?  Does it still lock up?

By the way, thanks for posting the samples and the netstat output.  You don't need to do that any more -- we've learned all we're going to learn from them.  :)
Logged

tiger_pers

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
Re: TIGER, Crashes 30 minutesafter launch
« Reply #11 on: July 25, 2005, 08:48:05 AM »
Hi,

Thanks for your help, I have tried to change some parameters (less slot, less upload capacities, less connection) and it looks to work fine at the moment.

So, if I encounter some new problems, I will contact you again.
Regards,
TIger
Logged
Imac G5, 1,8GHZ, 20"

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: TIGER, Crashes 30 minutesafter launch
« Reply #12 on: July 25, 2005, 10:10:11 PM »
OK.  I'm glad it's working for you now.  I wish I understood what was happening, but I'll settle for the problem going away.  ;)
Logged

Gomaaz

  • Jr. Member
  • **
  • Karma: 0
  • Offline Offline
  • Posts: 58
  • I want you to leave me alone...
Re: TIGER, Crashes 30 minutesafter launch
« Reply #13 on: August 18, 2005, 03:08:16 PM »
same prob just happened here  8o
Logged
Set UL-speed more higher than 10 kB/sec!! Remember:

You only get what you give  8)