linphone-users
[Top][All Lists]
Advanced

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

Re: [Linphone-users] Unhandled Exception in linphone.exe


From: Carriero Stefano TA . MSE_T_H14 . 1401
Subject: Re: [Linphone-users] Unhandled Exception in linphone.exe
Date: Tue, 1 Dec 2015 19:59:32 +0000

Hi,

 

Unfortunately, I was not able to reproduce the crash anymore after having uninstalled and re-installed linphone. However, I am still able to reproduce the decreasing voice quality. Following your instructions I recorded the debug logs on both ends. Please find attached the log files.

 

I think the interesting lines are:

-        In the file “LinPhone Debug 192.168.0.2.log”:

o   Line 215: [warning] 2015-12-01 20:09:53:527 belle_sip_socket_set_dscp(): not implemented.

o   Line 727: [error  ] 2015-12-01 20:10:58:003 Error in connect: Bad file descriptor

o   Line 967: [error  ] 2015-12-01 20:11:03:002 Error in connect: Invalid argument

o   Line 1468: [error  ] 2015-12-01 20:11:29:579 no such method on filter MSWASAPIWrite, fid=16394 method index=2

o   Line 1518: [warning] 2015-12-01 20:11:29:592 Getting reference signal but no echo to synchronize on.

o   Line 1519: [warning] 2015-12-01 20:11:29:592 Not enough ref samples, using zeroes

o   Line 1522: [warning] 2015-12-01 20:11:29:602 Not enough ref samples, using zeroes

 

-        In the file “LinPhone Debug 192.168.0.7.log”:

o   Line 195: warning: 2015-12-01 20:10:30:438 belle_sip_socket_set_dscp(): not implemented.

o   Line 701: error: 2015-12-01 20:11:25:337 no such method on filter MSWASAPIWrite, fid=16394 method index=2

o   Line 741: warning: 2015-12-01 20:11:25:351 Getting reference signal but no echo to synchronize on.

o   Line 742: warning: 2015-12-01 20:11:25:351 Not enough ref samples, using zeroes

o   Line 780: warning: 2015-12-01 20:11:25:882 ice: Received binding request missing MESSAGE-INTEGRITY attribute

o   Line 1073: warning: 2015-12-01 20:11:35:332 echo canceller: we are accumulating too much reference signal, need to throw out 5952 samples

o   [..]

o   Line 1208: warning: 2015-12-01 20:11:55:333 echo canceller: we are accumulating too much reference signal, need to throw out 12814 samples

o   Line 1249: warning: 2015-12-01 20:12:00:331 echo canceller: we are accumulating too much reference signal, need to throw out 21706 samples

o   Line 1281: warning: 2015-12-01 20:12:05:332 echo canceller: we are accumulating too much reference signal, need to throw out 64273 samples

o   Line 1282: warning: 2015-12-01 20:12:05:351 Too many samples to drop, dropping entire frame.

o   Line 1283: warning: 2015-12-01 20:12:05:431 Too many samples to drop, dropping entire frame.

o   […]

 

After disabling the echo canceller on both ends, I tried again and the result was that the connection was perfect in one direction. However, in the other direction I still had a decreasing voice quality as before.

Find these logs as well in the attachment (LinPhone Debug echo-off 192.168.0.2.log and LinPhone Debug echo-off 192.168.0.7.log).

 

I hope you see the root cause out of the logs. Thank you for your support.

 

Best regards

Stefano

 

On Behalf Of François Grisez
Sent: Dienstag, 1. Dezember 2015 10:49
To: address@hidden
Subject: Re: [Linphone-users] Unhandled Exception in linphone.exe

 

Hi,

 

We tried in our side without reproducing your issue. We need more information to investigate.

1.               Could you send us the logs of the two Linphone instances. You can display the debug window of Linphone by typing ctrl+d. For the crashing instance, you will need to launch Linphone from the command line to request it to write log messages in a file. See the procedure below:

a.                Open the Windows shell by typing ctrl+r and launching the program cmd.exe.

b.                type cd "c:\Program Files (x86)\Linphone"

c.                type bin\linphone.exe -l "c:\Users\<your_user_name>\Desktop\linphone.log"

d.                Once Linphone has crashed you will have a file in your desktop called linphone.log with the log messages inside.

2.               It could be also great to have the call stack trace at crash time. Normally you can get it with Visual Studio but your version of Linphone has no debug symbol. I will generate for you an installer to install a debug version in order you can get the call stack.

Best regards,

--

François Grisez

Software Engineer

Belledonne Communications

 


 

Le Monday 30 November 2015, 19:02:33 Carriero Stefano TA. MSE_T_H14. 1401 a écrit :

Hi François,

 

Thank you for your reply.

I did a direct connection between two Linphone clients running on Windows PC (without SIP Server). In the middle of the conversation the program crashed on one end, without doing anything… Maybe it is related to the other problem I posted on the mailing list two days ago. (see thread http://lists.nongnu.org/archive/html/linphone-users/2015-11/msg00077.html )

 

Best regards

Stefano

 

On Behalf Of François Grisez
Sent: Montag, 30.
November 2015 10:07
To:
address@hidden
Subject: Re: [Linphone-users] Unhandled Exception in linphone.exe

 

Hi Stefano,

 

I don't note any crash on my side. Is your crash occur after doing something in particular ? Can you send us a scenario which cause Linphone to crash ?

 

Regards,

--

François Grisez

Software Engineer

Belledonne Communications

 


 

Le Saturday 28 November 2015, 19:10:02 Carriero Stefano TA. MSE_T_H14. 1401 a écrit :

Today I had several crashes of Linphone 3.9.1 on Windows.

The information I got is the following: “An unhandled win32 exception occurred in linphone.exe [5808].”

 

Since I have MS Visual Studio on my computer, it asks me if I want to debug the crash. By starting the debugger I get the following additional information:

“Unhandled exception at 0x778AED0B (ntdll.dll) in linphone.exe: 0xC0000374: A heap has been corrupted (parameters: 0x778E4270).”

 

If I press “Continue”, the following message appears:

“Unhandled exception at 0x778129F2 (ntdll.dll) in linphone.exe: 0xC0000005: Access violation reading location 0xFFCEFFD1.”

 

Sounds like a bug.

Any Idea of what could be the problem?

 

 

Attachment: Linphone_logs.zip
Description: Linphone_logs.zip


reply via email to

[Prev in Thread] Current Thread [Next in Thread]