ios - Can Instruments be corrupting memory? -


as move next version of app closer submitting store run leak check on using instruments. on of test devices (ipod touch, iphone, ipad; different os levels, etc.) well, except on iphone 4s running ios 6.1.3, app crashes 75% of time.

the device logs showing commonality... doesn't make sense me.

the crashes of "unrecognized selector sent instance" variety, limit need scroll, i'll remove front part of message can see commonality more easily.

the first run crashed this:

reason: '-[uidevicewhitecolor clean]: unrecognized selector sent instance 0x1f84db50' 

the second run ran fine.

the third run crashed this:

reason: '-[calayer clean]: unrecognized selector sent instance 0x1f87fab0' 

the fourth run crashed variation:

reason: '-[uiimage clean]: unrecognized selector sent instance 0x1e56b9d0' 

lest think might calling private apple apis uidevicewhitecolor object, i'm not. have no idea coming from. @ time of crash network connection supposed being created between app , 1 on network app discovered using service discovery. connection class in fact have -clean method, calls method within connection class , of [self clean] variety -- it's hard see how -clean unrecognized selector sent oneself.

stackoverflow suggests race conditions may @ play when happens while instruments profiling app, i'm unclear how apply here.

can explain seeing versus red herrings?

p.s. reason ask if instruments corrupting memory because of cobweb-memories objective c's method dispatch table, , 3 crashes referencing weird , weirdly different objects, if dispatch table getting corrupted.

p.s.s. cold booted iphone 4s between third , fourth runs. i've quit both instruments , xcode make sure weren't twisted up.


Comments

Popular posts from this blog

java - Jmockit String final length method mocking Issue -

asp.net - Razor Page Hosted on IIS 6 Fails Every Morning -

c++ - wxwidget compiling on windows command prompt -