zhqiyi / webrtc2sip

Automatically exported from code.google.com/p/webrtc2sip
0 stars 0 forks source link

segfault error 4 in libtinyDAV.so.0.0.0 when more than 20 calls are fired within a second #120

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. More than 20 calls fired at a time within a second
2. More than 20 calls are disconnected at a time within a second

What is the expected output? What do you see instead?
Expected output from the application is to make 20 calls to the extensions we 
define. When I run a script from the bash to make 20calls from the FreeSWITCH 
CLI to the extensions that are registered through webrtc2sip to an OpenSIPS 
server and bridge them to a conference, the webrtc2sip application dies giving 
out the given below error:

webrtc2sip[29599]: segfault at 70 ip 00007f6f24a7834c sp 00007f6f19bc5d40 error 
4 in libtinyDAV.so.0.0.0[7f6f24a60000+40000]

I tried to turn on the debug signals through strace and gdb but I think I am 
doing something wrong with it that I cannot get more than this line in the logs 
and in the strace logs, could you please guys guide me or route me to a link 
where I can start debugging and see logs which are more than just segfault and 
actually see what created the above segfault error.

What version of the product are you using? On what operating system?

svn info output for webrtc2sip folder:
Path: .
URL: http://webrtc2sip.googlecode.com/svn/trunk
Repository Root: http://webrtc2sip.googlecode.com/svn
Repository UUID: 030ae762-4db0-52bf-379d-13dc8e1eab92
Revision: 103
Node Kind: directory
Schedule: normal
Last Changed Author: bossiel@yahoo.fr
Last Changed Rev: 100
Last Changed Date: 2013-06-17 21:58:31 +0000 (Mon, 17 Jun 2013)

Operating System:

Debian GNU/Linux 7.0 \n \l
Linux ls-test 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2+deb7u2 x86_64 GNU/Linux
2-core
4GB of RAM
Its a RackSpace cloud server

Please provide server logs with DEBUG level equal to INFO

The log says KILLED SIGSEGV or something and it dies, will provide you the 
exact error when I will try to test once more.

Please provide browser logs

Will provide you once tested again.

Original issue reported on code.google.com by aami...@gmail.com on 10 Aug 2013 at 10:58