Comment #8 on issue 20653 by bugdro...@chromium.org: Invalid read in
unixWrite and sqlite3MemSize in history::HistoryBackend::Init() on mac
http://code.google.com/p/chromium/issues/detail?id=20653
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&re
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: y
Comment #2 on issue 20653 by d...@chromium.org: Invalid read in unixWrite
and sqlite3MemSize in history::HistoryBackend::Init() on mac
http://code.google.com/p/chromium/issues/detail?id=20653
Seen again in
http://build.chromium.org/buildbot/waterfall.fyi/builders/Mac%20UI%201%20of%203%20(valgr
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
Status: Untriaged
Owner:
Labels: Type-Bug Pri-2 OS-Mac Area-Misc Size-Medium Valgrind
New issue 20653 by d...@chromium.org: Invalid read in unixWrite and
sqlite3MemSize in history::HistoryBackend::Init() on mac
http://code.google.com/p/chromium/issues/detail?id=20653
This was originally t
