Your message dated Mon, 17 Feb 2014 01:07:50 +0100
with message-id <[email protected]>
and subject line Re: Bug#718974: [Pkg-chromium-maint] Bug#718974: chromium:
segmentation fault in sql::Connection::GetCachedStatement on startup
has caused the Debian Bug report #718974,
regarding chromium: segmentation fault in sql::Connection::GetCachedStatement
on startup
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
718974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718974
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 28.0.1500.95-3
Severity: important
Chromium sometimes crashes on startup (segmentation fault).
I've attached a full backtrace, but here's where the crash occurs:
Core was generated by `/usr/lib/chromium/chromium --password-store=detect
https://www.vinc17.net/'.
Program terminated with signal 11, Segmentation fault.
#0 sql::Connection::GetCachedStatement (this=0x0, id=...,
sql=sql@entry=0x7f94ac725984 "SELECT COUNT(*) FROM favicons")
at /usr/include/c++/4.8/bits/stl_tree.h:1790
1790 find(const _Key& __k)
(gdb) bt
#0 sql::Connection::GetCachedStatement (this=0x0, id=...,
sql=sql@entry=0x7f94ac725984 "SELECT COUNT(*) FROM favicons")
at /usr/include/c++/4.8/bits/stl_tree.h:1790
#1 0x00007f94a90abe89 in history::ThumbnailDatabase::ComputeDatabaseMetrics (
this=<optimized out>) at chrome/browser/history/thumbnail_database.cc:240
#2 0x00007f94a9084285 in history::HistoryBackend::InitImpl (
this=this@entry=0x7f94b09e8060, languages=...)
at chrome/browser/history/history_backend.cc:758
#3 0x00007f94a908472d in history::HistoryBackend::Init (this=0x7f94b09e8060,
languages=..., force_fail=<optimized out>)
at chrome/browser/history/history_backend.cc:297
#4 0x00007f94a93da979 in Run (this=0x7f943d988388) at ./base/callback.h:396
#5 base::MessageLoop::RunTask (this=this@entry=0x7f943d9889e0,
pending_task=...) at base/message_loop.cc:484
#6 0x00007f94a93dbed0 in base::MessageLoop::DeferOrRunPendingTask (
this=this@entry=0x7f943d9889e0, pending_task=...)
at base/message_loop.cc:496
#7 0x00007f94a93dda75 in base::MessageLoop::DoWork (this=0x7f943d9889e0)
at base/message_loop.cc:688
#8 0x00007f94a93e0df1 in base::MessagePumpDefault::Run (this=0x7f9460014220,
delegate=0x7f943d9889e0) at base/message_pump_default.cc:29
#9 0x00007f94a93e0852 in base::MessageLoop::RunInternal (this=0x7f943d9889e0)
at base/message_loop.cc:441
#10 0x00007f94a93e08f5 in base::MessageLoop::RunHandler (this=<optimized out>)
at base/message_loop.cc:414
#11 0x00007f94a93f7538 in base::RunLoop::Run (this=this@entry=0x7f943d988820)
at base/run_loop.cc:45
#12 0x00007f94a93d9f85 in base::MessageLoop::Run (this=<optimized out>)
at base/message_loop.cc:321
#13 0x00007f94a940cf81 in base::Thread::ThreadMain (this=0x7f94b09e33c0)
at base/threading/thread.cc:197
#14 0x00007f94a9407d09 in base::(anonymous namespace)::ThreadFunc (
params=0x7f94b08300e0) at base/threading/platform_thread_posix.cc:95
#15 0x00007f94a29d6e0e in start_thread (arg=0x7f943d989700)
at pthread_create.c:311
#16 0x00007f94a168f93d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.10-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages chromium depends on:
ii chromium-inspector 28.0.1500.95-3
ii gconf-service 3.2.6-1
ii libasound2 1.0.27.2-1
ii libatk1.0-0 2.8.0-2
ii libc6 2.17-92
ii libcairo2 1.12.14-5+local1
ii libcups2 1.6.3-1
ii libdbus-1-3 1.6.12-1
ii libexpat1 2.1.0-4
ii libfontconfig1 2.10.2-2
ii libfreetype6 2.4.9-1.1
ii libgcc1 1:4.8.1-8
ii libgconf-2-4 3.2.6-1
ii libgcrypt11 1.5.3-1
ii libgdk-pixbuf2.0-0 2.28.2-1
ii libglib2.0-0 2.36.3-4
ii libgnome-keyring0 3.8.0-2
ii libgtk2.0-0 2.24.20-1
ii libjpeg8 8d-1
ii libnspr4 2:4.10-1
ii libnss3 2:3.15.1-1
ii libnss3-1d 2:3.15.1-1
ii libpango-1.0-0 1.32.5-5+b1
ii libpangocairo-1.0-0 1.32.5-5+b1
ii libspeechd2 0.7.1-6.2
ii libstdc++6 4.8.1-8
ii libudev0 175-7.2
ii libx11-6 2:1.6.0-1
ii libxcomposite1 1:0.4.4-1
ii libxdamage1 1:1.1.4-1
ii libxext6 2:1.3.2-1
ii libxfixes3 1:5.0.1-1
ii libxml2 2.9.1+dfsg1-3
ii libxrandr2 2:1.4.1-1
ii libxrender1 1:0.9.8-1
ii libxslt1.1 1.1.28-2
ii libxss1 1:1.2.2-1
ii xdg-utils 1.1.0~rc1+git20111210-7
chromium recommends no packages.
Versions of packages chromium suggests:
pn chromium-l10n <none>
-- no debconf information
gdb.txt.xz
Description: Binary data
--- End Message ---
--- Begin Message ---
On 2014-02-16 17:09:00 -0500, Michael Gilbert wrote:
> On Wed, Aug 7, 2013 at 6:46 AM, Vincent Lefevre wrote:
> > Chromium sometimes crashes on startup (segmentation fault).
> > I've attached a full backtrace, but here's where the crash occurs:
>
> I've never observed anything like this. Can you provide any more
> information. Also, have you seen it with newer chromium releases?
No, Chromium hasn't crashed for several months. So, I'm closing this bug.
--
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
