Re(2): Is there a transactional data limit with NSStreams?
Re(2): Is there a transactional data limit with NSStreams?
- Subject: Re(2): Is there a transactional data limit with NSStreams?
- From: Peter Lovell <email@hidden>
- Date: Tue, 08 Jul 2014 22:17:56 -0400
Sometimes the crusty old Curmudgeons are the best debuggers of all. They've seen most of it :)
Justin C. Walker <email@hidden> wrote:
>That error is almost always a result of accessing an invalid address
>(e.g., a write to a write-protected area, or accessing a "hole" in your
>address space).
Carl Hoefs <email@hidden> wrote:
>> On Jul 8, 2014, at 4:29 PM, Carl Hoefs
><email@hidden> wrote:
>>
>>> Could ARC be releasing the stream before its time?
>
>That was it! ARC was releasing the streams. But it was my fault!
>
>I had this:
>
> self.inputVideoNSStream = (__bridge NSInputStream
>*)self.readVideoCFStream;
> self.outputVideoNSStream = (__bridge NSOutputStream
>*)self.writeVideoCFStream;
>
>when I should have had this:
>
> self.inputVideoNSStream = (__bridge_transfer NSInputStream
>*)self.readVideoCFStream;
> self.outputVideoNSStream = (__bridge_transfer NSOutputStream
>*)self.writeVideoCFStream;
>
>I wasn't transferring the retain spec of the streams, so ARC axed them. D'oh!
>Thx,
>-Carl
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden