[TURN-Client] crash when tearing down a Session

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Quick question while I'm trying to figure this out. Do you have
multiprocessor/multicore system?

cheers
Benny

On Tue, Mar 17, 2009 at 4:36 PM, Michael Bradley Jr
<mbradley.jr at gmail.com>wrote:

> Hi Benny,
>
> Benny Prijono wrote:
> > Hi Michael, I also use XP regularly, and that's also what I did, testing
> > both the debug and release version of pjturn-client. I use pjturn-srv as
> my
> > TURN server though. What are you testing it against?
> >
>
> I'm testing against the r2519 pjturn-server...
> > If you have the console output from the client that would be useful.
> >
>
> Here is the console output and the call stack when the crash occurs. The
> crash occurs ALL the time, using an external STUN server doesn't change the
> test result.
>
> cheers,
> Mike
>
> <console>
> pjturn-client-i386-win32-vc8-debug.exe -T foobar:34780 -r pjsip.org  -u
> 701 -p 701 -F
>
>
> +====================================================================+
> |             CLIENT                |             PEER-0             |
> |                                   |                                |
> | State     : NULL                  | Address: 0.0.0.0:0             |
> | Relay addr: 0.0.0.0:0             |                                |
>  17:30:18.734          peer0  STUN mapped address found/changed:
> 10.0.23.42:9864
>  17:30:18.734  client_main.c  peer0: STUN Binding request success
> |                                   | 0  Send data to relay address  |
> | a      Allocate relay             +--------------------------------+
> | s,ss   Send data to peer 0/1      |             PEER-1             |
> | b,bb   BindChannel to peer 0/1    |                                |
> | x      Delete allocation          | Address: 0.0.0.0:0             |
> +-----------------------------------+                                |
> | q  Quit                  d  Dump  | 1  Send data to relay adderss  |
> +-----------------------------------+--------------------------------+
> >>>  17:30:18.734  client_main.c  peer0: STUN mapped address is
> 10.0.23.42:9864
>  17:30:18.734          peer1  STUN mapped address found/changed:
> 10.0.23.42:9865
>  17:30:18.734  client_main.c  peer1: STUN Binding request success
>  17:30:18.734  client_main.c  peer1: STUN mapped address is
> 10.0.23.42:9865
> a
>  17:30:25.671 tcprel009FC630  TURN client session created
>  17:30:25.671 tcprel009FC630  State changed Null --> Resolving
>  17:30:25.671  client_main.c  State Null --> Resolving
>  17:30:25.671 tcprel009FC630  State changed Resolving --> Resolved
>  17:30:25.687  client_main.c  State Resolving --> Resolved
>
>
> +====================================================================+
> |             CLIENT                |             PEER-0             |
> |                                   |                                |
> | State     : Resolved              | Address: 10.0.23.42:9864  |
> | Relay addr: 0.0.0.0:0             |                                |
> |                                   | 0  Send data to relay address  |
> | a      Allocate relay             +--------------------------------+
> | s,ss   Send data to peer 0/1      |             PEER-1             |
> | b,bb   BindChannel to peer 0/1    |                                |
> | x      Delete allocation          | Address: 10.0.23.42:9865  |
> +-----------------------------------+                                |
> | q  Quit                  d  Dump  | 1  Send data to relay adderss  |
> +-----------------------------------+--------------------------------+
> >>>  17:30:25.687 tcprel009FC630  State changed Resolved --> Allocating
>  17:30:25.687  client_main.c  State Resolved --> Allocating
>  17:30:25.687 tcprel009FC630  Retrying request with new authentication
>  17:30:25.718 tcprel009FC630  State changed Allocating --> Ready
>  17:30:25.718  client_main.c  State Allocating --> Ready
>  17:30:27.296 stuntsx009FAFF  STUN timeout waiting for response
>  17:30:27.296 stuntsx00A1004  STUN timeout waiting for response
>  17:30:33.734  client_main.c  peer0: Keep-alive success
>  17:30:33.734  client_main.c  peer1: Keep-alive success
>  17:30:48.734  client_main.c  peer0: Keep-alive success
>  17:30:48.734  client_main.c  peer1: Keep-alive success
>  17:31:03.734  client_main.c  peer0: Keep-alive success
>  17:31:03.734  client_main.c  peer1: Keep-alive success
>  x
>  17:31:15.875 tcprel009FC630  Request to shutdown in state Ready, cause:0
>  17:31:15.875 tcprel009FC630  State changed Ready --> Deallocating
>  17:31:15.875  client_main.c  State Ready --> Deallocating
>  17:31:15.875  client_main.c  Relay shutting down..
>
>
> +====================================================================+
> |             CLIENT                |             PEER-0             |
> |                                   |                                |
> | State     : NULL                  | Address: 10.0.23.42:9864  |
>  17:31:15.875 tcprel009FC630  State changed Deallocating --> Deallocated
>  17:31:15.875  client_main.c  State Deallocating --> Deallocated
>  17:31:15.875 tcprel009FC630  Request to shutdown in state Deallocated,
> cause:0
> | Relay addr: 0.0.0.0:0             |                                |
> |                                   | 0  Send data to relay address  |
>  17:31:15.875 tcprel009FC630  sess_shutdown 4 timer count tid 1
>  17:31:15.875 tcprel009FC630  State changed Deallocated --> Destroying
> | a      Allocate relay             +--------------------------------+
> | s,ss   Send data to peer 0/1      |             PEER-1             |
> | b,bb   BindChannel to peer 0/1    |                                |
> | x      Delete allocation          | Address: 10.0.23.42:9865  |
> +-----------------------------------+                                |
> | q  Quit                  d  Dump  | 1  Send data to relay adderss  |
>  17:31:15.875  client_main.c  State Deallocated --> Destroying
> +-----------------------------------+--------------------------------+
> >>>  17:31:15.875 tcprel009FC630  TURN client session destroyed
>  17:31:15.875 turn_session.c  on_timer_event 3 timer count
> </console>
>
>
> <call_stack>
> >
> pjturn-client-i386-win32-vc8-debug.exe!push_freelist(pj_timer_heap_t *
> ht=0x009f38f4, int old_id=-17891602)  Line 149 + 0x11 bytes      C
>        pjturn-client-i386-win32-vc8-debug.exe!remove_node(pj_timer_heap_t *
> ht=0x009f38f4, unsigned int slot=0)  Line 214 + 0x10 bytes C
>
>  pjturn-client-i386-win32-vc8-debug.exe!pj_timer_heap_poll(pj_timer_heap_t *
> ht=0x009f38f4, pj_time_val * next_delay=0x00000000)  Line 513 + 0xb bytes
> C
>        pjturn-client-i386-win32-vc8-debug.exe!worker_thread(void *
> unused=0x00000000)  Line 231 + 0xd bytes    C
>        pjturn-client-i386-win32-vc8-debug.exe!thread_main(void *
> param=0x009f4038)  Line 414 + 0x11 bytes      C
>        kernel32.dll!7c80b713()
>        [Frames below may be incorrect and/or missing, no symbols loaded for
> kernel32.dll]
> </call_stack>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20090317/c05cc1ab/attachment.html>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux