On Aug 24, 2015, at 11:50 AM, Roger Binns <rogerb at rogerbinns.com> wrote: > On 08/24/2015 03:08 AM, Jeff M wrote: >> I've checked all of your suggestions and nothing is amiss. > > You ran valgrind and it said everything is fine? That would be shocking.
You caught me. I wasn't familiar with valgrind, so I passed over that suggestion. I tried to install valgrind (on Mac OS Yosemite), but I can't get it to compile. I don't have the fortitude to work out the install issues. Looking at Xcode's memory report (and using Instruments), I see that memory does ratchet up, despite my being very careful matching alloc/releases (this app is pre-ARC). I need to relearn Instruments. Among other things, I see many persistent 4K memory blocks resulting from sqlite3MemRealloc, but I haven't figured out the call tree to get there. On Aug 24, 2015, at 11:50 AM, Roger Binns <rogerb at rogerbinns.com> wrote: > ... there is [likely] a bug in [your] code related to object/pointer > lifetimes or similar. [C]hanging things changes where collateral damage > happens, but doesn't actually fix the issue. Yup. Jeff
