Re: Does file-mapping a memory allocation work around RAM limits?

Thanks for that thorough explanation! We're going to try using mmap(). It will be interesting to do this from Swift. > On May 4, 2017, at 10:04 , David Duncan wrote: > > >> On May 3, 2017, at 11:51 PM, Rick Mann wrote: >> >>> >>> On May 3,

Re: Does file-mapping a memory allocation work around RAM limits?

> On May 3, 2017, at 11:51 PM, Rick Mann wrote: > >> >> On May 3, 2017, at 23:27 , Doug Hill wrote: >> >> >>> On May 3, 2017, at 6:21 PM, Rick Mann wrote: >>> >>> Our iOS app works with very large data buffers (hundreds of

Re: Does file-mapping a memory allocation work around RAM limits?

To answer the OP’s original question, I’m not sure about the exact rules Apple is using on iOS, but I’d expect the memory limit to apply to *private* memory, namely that allocated using malloc() et al, plus dirty pages mapped with mmap()’s MAP_PRIVATE flag. Read-only and shared mappings that

Re: Does file-mapping a memory allocation work around RAM limits?

> On May 3, 2017, at 23:27 , Doug Hill wrote: > > >> On May 3, 2017, at 6:21 PM, Rick Mann wrote: >> >> Our iOS app works with very large data buffers (hundreds of MB). As you can >> imagine, we run into issues at times. >> >> I saw some sample

Re: Does file-mapping a memory allocation work around RAM limits?

> On May 3, 2017, at 6:21 PM, Rick Mann wrote: > > Our iOS app works with very large data buffers (hundreds of MB). As you can > imagine, we run into issues at times. > > I saw some sample code that used this technique, and it got me wondering if > this actually works

Does file-mapping a memory allocation work around RAM limits?

Our iOS app works with very large data buffers (hundreds of MB). As you can imagine, we run into issues at times. I saw some sample code that used this technique, and it got me wondering if this actually works around the 600 MB limitation of some iOS devices (which begs another question: doss