Bug#676636: segfault repeatedly when using the omnibox (in sqlite code?)

Vincent Bernat writes: > I am also hit by this bug. It seems to have been fixed upstream: > http://code.google.com/p/chromium/issues/detail?id=122525 > > I am trying to compile the patch right now to see if it fixes this > issue. After a few hours of compilation, this patch seems to fix this is

Bug#676636: segfault repeatedly when using the omnibox (in sqlite code?)

Hi Vincent, Vincent Bernat wrote: > I am also hit by this bug. It seems to have been fixed upstream: > http://code.google.com/p/chromium/issues/detail?id=122525 This bug is not present in Debian's sqlite3 package. The problem is that chromium is using a bundled copy instead of the system lib.

Bug#676636: segfault repeatedly when using the omnibox (in sqlite code?)

Package: chromium Version: 20.0.1132.21~r139451-3 Followup-For: Bug #676636 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! I am also hit by this bug. It seems to have been fixed upstream: http://code.google.com/p/chromium/issues/detail?id=122525 I am trying to compile the patch right now to

Bug#676636: segfault repeatedly when using the omnibox (in sqlite code?)

Package: chromium Version: 20.0.1132.21~r139451-3 Severity: serious The new chromium browser segfault very frequently and in a reproducible manner while using the omnibox, apparently while searching through the underlying sqlite database of browsing history. (I've a couple of queries that reliably