Bad Access Error on listen thread when pinging multiple IPs about gbping

[PabloAlejandro]

Same issue here

EXC_BAD_ACCESS (code=1, address=0x0)

[mikumi]

I'm having this issue as well, but haven't found out why it's happening yet

[cpage13]

Same here. It is very difficult to consistently reproduce. I have a feeling it has to do with the fact that pendingPings been accessed and mutated in different threads. Maybe wrapping them in @synchronized could help?

[lmirosevic]

Can you see if 1.3.1 still exhibits this behaviour?

[cpage13]

So far looks good. Thanks for looking into this.

[ftnn]

1.3.3 still has this issue;

Crashed: listenThread

EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000000

0 CoreFoundation -[__NSDictionaryM objectForKey:] + 229
1 GBPing.m line 382 -[GBPing listenOnce]
2 GBPing.m line 346 -[GBPing listenLoop]

@synchronized(self) is needed to protect multi-thread access

[alexjessecole]

This is indeed still an issue in 1.3.3.

Crashed: listenThread
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000000

Any help getting this cleared up would be amazing and greatly appreciated!