epiphany-browser crashed with SIGSEGV

[Cristian Aravena Romero]

I'm working with ephipany and crash.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: epiphany-browser 3.6.1-2ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3
Uname: Linux 3.8.0-0-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Fri Jan 18 10:11:22 2013
ExecutablePath: /usr/bin/epiphany-browser
InstallationDate: Installed on 2012-11-27 (52 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121126)
MarkForUpload: True
ProcCmdline: epiphany-browser
SegvAnalysis:
 Segfault happened at: 0x46430b: mov 0x90(%rbx),%esi
 PC (0x0046430b) ok
 source "0x90(%rbx)" (0xaaaaaaaaaaaaab3a) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: epiphany-browser
Stacktrace:
 #0 0x000000000046430b in ?? ()
 No symbol table info available.
 No se puede acceder a la memoria en la dirección 0x7fffb1d51ec8
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Hilo 14 (LWP 3578):
 #0 0x00007f2e52e1f2fd in ?? ()
 No symbol table info available.
 .
Title: epiphany-browser crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Stacktrace:
 #0 0x000000000046430b in pop_statusbar_later_cb (data=<error reading variable: Cannot access memory at address 0x7fffb1d51ec8>) at ephy-embed.c:699
         embed = 0x242cbc0
         priv = 0xaaaaaaaaaaaaaaaa
 Cannot access memory at address 0x7fffb1d51ec8
StacktraceTop: pop_statusbar_later_cb (data=<error reading variable: Cannot access memory at address 0x7fffb1d51ec8>) at ephy-embed.c:699
ThreadStacktrace:
 .
 Thread 14 (LWP 3578):
 #0 0x00007f2e52e1f2fd in ?? ()
 No symbol table info available.
 .

[Paul White (paulw2u)]

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

[Paul White (paulw2u)]

Won't expire due to bug watch so closing.