Comment #1 on issue 20653 by daniel.r.kegel: Invalid read in unixWrite and sqlite3MemSize in history::HistoryBackend::Init() on mac http://code.google.com/p/chromium/issues/detail?id=20653
Filed as http://sqlite.org/cvstrac/tktview?tn=4039 but it's not at all clear it's sqlite's problem. This only happens on the Mac, even though similar code is in use on Linux. It seems odd that bytes in the middle of a block allocated by malloc() could be unaddressible. Something strange is going on...? -- 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 -~----------~----~----~----~------~----~------~--~---
