May I just jump in to say that you probably should be discussing this on the
macnetworkprog list? There are people on that list (esp. Quinn) who are experts
in this area.
—Jens
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post
> On 13 Jan 2015, at 13:05, Graham Cox wrote:
>
>
>> On 13 Jan 2015, at 8:11 pm, Mike Abdullah wrote:
>>
>> One small suggestion: I think the frameworks would prefer it if you copied
>> the ephemeralSessionConfiguration, and then modified the copy. Modifying
>> this shared config is probabl
> On 13 Jan 2015, at 8:11 pm, Mike Abdullah wrote:
>
> One small suggestion: I think the frameworks would prefer it if you copied
> the ephemeralSessionConfiguration, and then modified the copy. Modifying this
> shared config is probably not supported, and while it might work now, might
> not
leaks, not bugs.
Kevin
On 13 Jan 2015, at 10:21, Kevin Meaney wrote:
> On 13 Jan 2015, at 02:51, Graham Cox wrote:
>>
>>> On 13 Jan 2015, at 12:21 pm, Roland King wrote:
>>>
>>> Did you read the devforums thread I pointed you at a couple of weeks ago?
>>
>>
>> Umm, not sure Roland. I read
On 13 Jan 2015, at 02:51, Graham Cox wrote:
>
>> On 13 Jan 2015, at 12:21 pm, Roland King wrote:
>>
>> Did you read the devforums thread I pointed you at a couple of weeks ago?
>
>
> Umm, not sure Roland. I read the blog post by bbum about using Allocations,
> which is the one you linked in
> On 13 Jan 2015, at 01:00, Graham Cox wrote:
>
> I'm still having an issue with this - I think.
>
> I've exhaustively hunted down every leak and memory allocation in my app -
> luckily it's a fairly small one, though one that can create many threads -
> and have eliminated everything I have
> On 13 Jan 2015, at 11:20, Graham Cox wrote:
>
> Thanks - sorry I missed it in the first mail for some reason.
>
> An interesting thread. This remark from Quinn stood out for me:
>
> "If you stop issuing new requests, NSURL{Session,Connection} quickly recovers
> this memory to the point wher
Thanks - sorry I missed it in the first mail for some reason.
An interesting thread. This remark from Quinn stood out for me:
"If you stop issuing new requests, NSURL{Session,Connection} quickly recovers
this memory to the point where, at the end of a cycle like this, the memory use
(as shown b
https://devforums.apple.com/message/1056669#1056669
No that one from the same mail.
> On 13 Jan 2015, at 10:51, Graham Cox wrote:
>
>
>> On 13 Jan 2015, at 12:21 pm, Roland King wrote:
>>
>> Did you read the devforums thread I pointed you at a couple of weeks ago?
>
>
> Umm, not sure Ro
> On 13 Jan 2015, at 12:21 pm, Roland King wrote:
>
> Did you read the devforums thread I pointed you at a couple of weeks ago?
Umm, not sure Roland. I read the blog post by bbum about using Allocations,
which is the one you linked in this thread. Did you mean something else?
Forgive me, I c
Did you read the devforums thread I pointed you at a couple of weeks ago? I
noted it was iOS not OSX however my general belief is as time goes by, more and
more code is common to the platforms so if there’s a bug in iOS at 8.x (and
there is) it may also exist on OSX at some recent version. On th
I'm still having an issue with this - I think.
I've exhaustively hunted down every leak and memory allocation in my app -
luckily it's a fairly small one, though one that can create many threads - and
have eliminated everything I have control over*
My heap space is still growing over time. I'm
> On 2 Jan 2015, at 1:46 pm, Roland King wrote:
>
> Having a handler block which refers to self is not in and of itself a
> problem, very many blocks implicitly do. The block retains self, however in
> most cases something else retains the block and the self reference goes away
> when the blo
> On Jan 1, 2015, at 18:26, Graham Cox wrote:
>
>
>> On 2 Jan 2015, at 12:48 pm, Quincey Morris
>> wrote:
>>
>> That usually means the block and the ‘self’ it captured mutually refer
>> to each other. I’m betting this is what’s wrong in your case.
>>
>>
>
>
> Quincey, thanks for yo
> On 2 Jan 2015, at 10:52, Joar Wingfors wrote:
>
>
>> On 1 jan 2015, at 18:22, Roland King wrote:
>>
>> +1 for all of this. I wouldn't call leaks an utter waste of time, but it
>> really does only find pure retain cycles (which it then annotates very
>> nicely) and not memory which is real
> On 1 jan 2015, at 18:22, Roland King wrote:
>
> +1 for all of this. I wouldn't call leaks an utter waste of time, but it
> really does only find pure retain cycles (which it then annotates very
> nicely) and not memory which is really is pinned by a real reference which is
> more often the
> On 1 jan 2015, at 18:26, Graham Cox wrote:
>
>
>> On 2 Jan 2015, at 12:48 pm, Quincey Morris
>> wrote:
>>
>> That usually means the block and the ‘self’ it captured mutually refer
>> to each other. I’m betting this is what’s wrong in your case.
>>
>>
>
>
> Quincey, thanks for you
>
> My handler block refers to 'self' quite extensively - it calls other methods
> of self and also refers to properties such as self.delegate. I'm not quite
> sure how I can rework it not to refer to self. Maybe I just need to not use
> the completion block approach and use a delegate callbac
> On 2 Jan 2015, at 12:48 pm, Quincey Morris
> wrote:
>
> That usually means the block and the ‘self’ it captured mutually refer
> to each other. I’m betting this is what’s wrong in your case.
>
>
Quincey, thanks for your lengthy and well-thought-out reply (as usual) :)
I think you'v
+1 for all of this. I wouldn't call leaks an utter waste of time, but it really
does only find pure retain cycles (which it then annotates very nicely) and not
memory which is really is pinned by a real reference which is more often the
case. Also, if you're using KVO anywhere, this tends to ent
A while back I had a similar sounding issue in an iOS project I was working on.
The memory usage kept growing, although I could find no obvious culprits in my
code after hours of exploration. My solution probably doesn’t pertain to you,
but I thought I’d pass it along just in case it’s something
On Jan 1, 2015, at 17:20 , Graham Cox wrote:
>
> I'm using Allocations, but I'm finding the volume of data a bit overwhelming.
>
> As an aside, Leaks shows nothing at all. Does that mean I'm not actually
> leaking anything?
Forget Leaks, it’s an utter waste of time*. Use marked generations
> On 2 Jan 2015, at 10:52 am, David Duncan wrote:
>
> The first thing to keep in mind is that unless otherwise qualified, all
> object references are owned - locals, ivars, array entries, etc. The places
> where this isn’t possible (such as structs) are flagged as compiler errors.
> The lifet
> On Jan 1, 2015, at 3:38 PM, Graham Cox wrote:
>
> Hi all,
>
> I know I'm very, very late to the party, but I'm building my first ever
> project with ARC instead of manual retain/release (which I was always very
> comfortable with). Frankly, I'm finding it frustrating because it seems much
24 matches
Mail list logo
