Comment #3 on issue 20653 by drhsqlite: Invalid read in unixWrite and sqlite3MemSize in history::HistoryBackend::Init() on mac http://code.google.com/p/chromium/issues/detail?id=20653
See http://www.sqlite.org/src/vinfo/5e2f54968 and let us know if this clears the problem. Unrelated note: you might consider using the SQLite amalgamation instead of separate source files. By combining all of the SQLite source files into a single big file of the amalgamation, the compiler is able to do much better cross-procedure optimization and as a result the whole thing runs about 10% faster. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
