Bug fix here: http://www.sqlite.org/src/info/120c82d56e
This fix will appear in SQLite version 3.7.16, sometime next year. On Tue, Dec 11, 2012 at 7:10 PM, Phil Schwan <[email protected]> wrote: > Using sqlite 3.7.14.1 2012-10-04 19:37:12 > 091570e46d04e84b67228e0bdbcd6e1fb60c6bdb on a 16 GB Linux-64 desktop. > > I'm having a problem that bears a passing similarity to > http://osdir.com/ml/sqlite-users/2012-04/msg00094.html > > But unlike that user, my database is only 15 MB. > > If I run integrity_check(833), it prints 833 messages. If I run > (834), it runs out of memory before printing any. > > ltrace doesn't really indicate why this is so; all malloc()s and > realloc()s are shown as successful. Valgrind reports that it never > uses more than 28 MB. There are no heap or stack ulimits for this > user. > > I can try it on a machine with 256 GB physical memory, but given the > above, that doesn't seem very likely to be the issue. > > Any enlightened thoughts, or something I might do to help debug? The > database itself can be found at > https://secure.dugeo.com/download/corrupted.sqlite3.gz > > Cheers, > > -Phil > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
