QMC妹妹，我能跟你炒一下价吗 - 未名空间MITBBS历史存档

国际科技财经博客移民网络热点娱乐民生时事公众号

Redian新闻

>未名空间

>Piebridge - 鹊桥

QMC妹妹，我能跟你炒一下价吗

QMC妹妹，我能跟你炒一下价吗# Piebridge - 鹊桥

c*g2012-07-03 07:07

1 楼

最近一个memory leak的问题搞得我头大，有人愿意看看吗？给出有效线索或解决方案
的发大包子。
http://stackoverflow.com/questions/6302545/crazy-leak-detection

z*a2012-07-03 07:07

2 楼

青青子吟已经炒上去了，我们什么时候吵吵架？

S*r2012-07-03 07:07

3 楼

I suggest you
1. move backgroundImageView.hidden = !selected;
to within
- (void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event
because it's not a good idea to manipulate UI in a data member's setter.
2. let system generate setter and getter for you.

c*g2012-07-03 07:07

4 楼

I moved the backgroundImageView.hidden = !selected to the touchesBegan: call
. However, now the leaks
instrument reports the touchesBegan is leaking. According to the report, the
leaking statement is
"backgroundImageView.hidden = !selected". That's why I am confused.
I also posted this to Apple's developer forum. One guy mentioned if an
object leaks, all its sub-objects will
leak as well. But I just couldn't find out the root cause.
Thanks anyway.

【在 S**********r 的大作中提到】

: I suggest you
: 1. move backgroundImageView.hidden = !selected;
: to within
: - (void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event
: because it's not a good idea to manipulate UI in a data member's setter.
: 2. let system generate setter and getter for you.

i*o2012-07-03 07:07

5 楼

What happens when background image is shown or hidden, maybe once it is
shown, some view will have a reference to it, and that guy is not releasing
it.
So basically follow the chain reaction caused by this call...

【在 c********g 的大作中提到】

: 最近一个memory leak的问题搞得我头大，有人愿意看看吗？给出有效线索或解决方案
: 的发大包子。
: http://stackoverflow.com/questions/6302545/crazy-leak-detection