epiphany-browser crashed with signal 5 in ephy_sqlite_connection_table_exists()

Bug #1237729 reported by Michael Gratton
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Epiphany Browser
Expired
Critical
Ubuntu GNOME
New
Undecided
Unassigned

Bug Description

Ephy is configured to be the default browser on my system. An Ephy instance was running and loading a few pages. I clicked on a link in Thunderbird while this was happening and (I presume) the instance of Ephy that was spawned, rather than forwarding the page load request to the existing instance, crashed instead.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: epiphany-browser-webkit2 3.9.91-0ubuntu1~saucy1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Oct 10 11:15:36 2013
ExecutablePath: /usr/bin/epiphany-browser
InstallationDate: Installed on 2011-06-03 (859 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MarkForUpload: True
ProcCmdline: epiphany-browser http://urbanwalkabout.us1.list-manage1.com/track/click?u=d6eb5a59806ae6ba8cd54a22f&id=8ea2f4971f&e=68a6959234
Signal: 5
SourcePackage: epiphany-browser
StacktraceTop:
 ephy_sqlite_connection_table_exists (self=<optimised out>, table_name=table_name@entry=0x4a088b "hosts") at /build/buildd/epiphany-browser-3.9.91/./lib/ephy-sqlite-connection.c:176
 ephy_history_service_initialize_hosts_table (self=self@entry=0x21a6f50) at /build/buildd/epiphany-browser-3.9.91/./lib/history/ephy-history-service-hosts-table.c:34
 ephy_history_service_open_database_connections (self=0x21a6f50) at /build/buildd/epiphany-browser-3.9.91/./lib/history/ephy-history-service.c:375
 run_history_service_thread (self=0x21a6f50) at /build/buildd/epiphany-browser-3.9.91/./lib/history/ephy-history-service.c:454
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: epiphany-browser crashed with signal 5 in ephy_sqlite_connection_table_exists()
UpgradeStatus: Upgraded to saucy on 2013-10-02 (7 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare video

Revision history for this message
Michael Gratton (mjog) wrote :
information type: Private → Public
Revision history for this message
Ubuntu GNOME (ug-bot) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 _r_debug ()
 ?? ()
 ephy_sqlite_connection_table_exists (self=<optimized out>, table_name=0x7f60780144c0 "database is locked", table_name@entry=0x4a088b "hosts") at /build/buildd/epiphany-browser-3.9.91/./lib/ephy-sqlite-connection.c:176

Revision history for this message
Ubuntu GNOME (ug-bot) wrote : Stacktrace.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : StacktraceSource.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Michael Gratton (mjog) wrote :

As I mentioned in Bug #1247301, this happens when there is an Ephy instance running and loading a page, then another instance is spawned (as a result of clicking on a link in another application). The new instance crashes, not the previously existing instance.

summary: - epiphany-browser crashed with signal 5 in
- ephy_sqlite_connection_table_exists()
+ epiphany-browser crashed opening a link from an external program
description: updated
Barneedhar (barneedhar)
summary: - epiphany-browser crashed opening a link from an external program
+ epiphany-browser crashed with signal 5 in
+ ephy_sqlite_connection_table_exists()
Changed in epiphany-browser:
importance: Unknown → High
status: Unknown → New
Changed in epiphany-browser:
status: New → Invalid
Revision history for this message
Michael Gratton (mjog) wrote :

Original b.g.o bug was dup'ed.

Changed in epiphany-browser:
importance: High → Unknown
status: Invalid → Unknown
Changed in epiphany-browser:
importance: Unknown → Critical
status: Unknown → New
Changed in epiphany-browser:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.