Trying to find memory leaks by looking at the OS memory statistics is pointless. It's like looking at satellite photos to find a dropped contact lens. :) The kernel's virtual memory system (on any modern OS) is very complex, and the behavior of malloc/free in a process is also complex.
If you want to look for memory leaks, the best way is to use (platform-specific) instrumentation tools for that purpose. I'm a Mac/iOS developer so I use the 'leaks' tool and Instruments app; I don't know how this is done on Linux. You can also look at the process's overall heap size (again, the name of this varies by platform, it's called RPRVT on Mac OS) and see if it's growing monotonically over time. But this is only a rough guide, as malloc/free don't always free up address space when heap blocks are freed. —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
