nmkhoa / unitt

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

EXC_BAD_ACCESS on pingTimer object #45

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. connect 
2. wait for the connection to be closed
3. stopPingTimer will be called
4. [pingTimer release] will crash the program (because it wasn't retained in 
the first place)

What is the expected output? What do you see instead?
expected [pingTimer release] not to crash

What version of the product are you using? On what operating system?
I used 1.0.0-rc2 (with *.a library files) and had the same problem.
And used source files(*.m) in the svn trunk. 
operating system: iOS

Please provide any additional information below.
For discussion of proper timer release,
http://stackoverflow.com/questions/1171393/what-is-the-first-step-in-nstimer-rel
ease-and-invalidate

Original issue reported on code.google.com by p.compas...@gmail.com on 15 Jun 2012 at 6:01

GoogleCodeExporter commented 8 years ago
*facepalm* I'll get it fixed.

Original comment by joshuadmorris@gmail.com on 18 Jun 2012 at 3:50

GoogleCodeExporter commented 8 years ago

Original comment by joshuadmorris@gmail.com on 20 Jun 2012 at 6:13