On Tuesday, July 27, 2010 6:43 PM, Richard Hipp wrote: >> [ ... ] >> >> However, I have also attached journaltest2.log which I think does >> demonstrate the memory leak. Having trawled through the full log file, >> it >> seems that the memory leak is coming from the FTS3 tests, so the >> journaltest2.log file is the output from: >> >> ./testfixture test/permutations.test journaltest fts3cov.test >> fts3malloc.test memsubsys2.test >> >> I tried a similar run with inmemory_journal instead of journaltest, but >> this gave me a "database disk image is malformed" error (see >> inmemory_journal2.log), but this is not an error I received when running >> the >> full test suite, so it is probably because I'm running a test sequence >> that >> I shouldn't. > > > Correct. fts3cov.test is not compatible with inmemory_journal. >
So does this mean that the memory leak that comes out when running "make fulltest" or through "./testfixture test/permutations.test journaltest fts3cov.test fts3malloc.test memsubsys2.test" is not really a memory leak, just an incompatible test that has made it into the test suite? Oh, and thanks for merging my suggested change for "configure" into your repository - I spotted it on my daily browse through. Regards Andy _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
