|
From: Adam R. M. <ama...@me...> - 2016-04-04 15:07:20
|
> On Apr 4, 2016, at 07:54 , Christiaan Hofman <cmh...@gm...> wrote: > > >> On Apr 4, 2016, at 16:38, Adam R. Maxwell <ama...@me... <mailto:ama...@me...>> wrote: >> >> >>> On Apr 4, 2016, at 03:24 , Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote: >>> >>> I wonder if it would make sense, perhaps as a workaround, to retain the icon while it’s working with the web view, and releasing itself when it’s done. But I’m not sure where that would be, and if it would not be hanging around too long with such an arrangement. >> >> I guess I can try to reproduce it with a trivial project, which Apple would want for a bug report (though I've given up on filing those). There's an extra refcount decrement coming from something, so releasing self might also trigger it :(. As an emergency fix, I guess just making dealloc a no-op would do it; that's a relatively minor leak, assuming -releaseResources gets sent. > > So this is really an over-release, not balanced with a retain? AFAICT, yes, since it happens after the icon is done with the webview. It looks like it has a couple of extra releases, though. WTF. I still have a faint hope that there's a missing delegate call or something that would fix it, or maybe a bug elsewhere. If it were in the view/controller/operation level, though, it should show up with other icon classes :/. -- adam |