On Mon, Oct 24, 2016 at 4:28 PM, Wade, William <bill.w...@dnvgl.com> wrote: > It sounds like you've got a way forward on leaks via the malloc() system > within the process space. > > 1) The region of the C process stack that was reached by some deep call stack. > 2) Processor registers. > 3) Process pages that were copied to disk by the OS (this could be a problem > even if you otherwise have a good handle on clearing malloc() blocks). >
Good points, thanks, especially (3) as having more likely scenario to contain all kind of data and lengths. Probably in case of predictable memory requirements this one can be handled by providing zero-malloc implementation with a physically locked region of memory (in case of Windows - VirualLock API). _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users