nmkhoa / unitt

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

if force close server, app dies in iOSsimulator #54

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. run app, websocket is open
2. Close server forced (ctrl-c)
3.

What is the expected output? What do you see instead?
thread7:exc_bad_access

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

Please provide any additional information below.

Original issue reported on code.google.com by silvafaf...@gmail.com on 20 Dec 2012 at 11:24

GoogleCodeExporter commented 8 years ago
Can I reproduce this with any server or do I need to run a specific one?

Original comment by joshuadmorris@gmail.com on 21 Dec 2012 at 5:57

GoogleCodeExporter commented 8 years ago
just tried with the tronado...
after i stopped testing unitt because not doing to build amr7

Original comment by silvafaf...@gmail.com on 26 Dec 2012 at 10:07

GoogleCodeExporter commented 8 years ago
I returned to work with unitt, the problem happens when I force closing of the 
server (ctrl-c on server).

Thread 10, Queue : GCDAsyncSocket

Original comment by silvafaf...@gmail.com on 28 Dec 2012 at 4:54

Attachments:

GoogleCodeExporter commented 8 years ago
I have a picture to help

Original comment by silvafaf...@gmail.com on 2 Jan 2013 at 1:48

Attachments:

GoogleCodeExporter commented 8 years ago
I think the problem comes from
[pingTimer invalidate];

if i comment calling to function [self stopPingTimer]; in dispatchClosed 
aplication not breack

Original comment by silvafaf...@gmail.com on 2 Jan 2013 at 2:53

GoogleCodeExporter commented 8 years ago
I will check it out and get a fix out shortly.

Original comment by joshuadmorris@gmail.com on 7 Jan 2013 at 9:57

GoogleCodeExporter commented 8 years ago
This is also happening for me. Any news of a fix.

Original comment by mrwel...@gmail.com on 23 Jan 2013 at 1:55

GoogleCodeExporter commented 8 years ago
I'm also getting this error after server shuts down the connection due to 
inactivity...

Original comment by hwk.i...@googlemail.com on 19 Feb 2013 at 9:51