webbrowser-app crashed with SIGSEGV

[Till Kamppeter]

I was watching a video (720p) on YouTube with the Ubuntu web browser app on Saucy with standard Unity desktop. When closing the app with the video still playing the sound continued to play until I started the app again. Then the crash happened.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: webbrowser-app 0.22+13.10.20130809.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
Uname: Linux 3.11.0-1-generic x86_64
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Tue Aug 13 15:09:34 2013
ExecutablePath: /usr/bin/webbrowser-app
InstallationDate: Installed on 2013-06-05 (68 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130605)
MarkForUpload: True
ProcCmdline: webbrowser-app
SegvAnalysis:
 Segfault happened at: 0x7f097981de7a: mov 0x8(%rax),%rbx
 PC (0x7f097981de7a) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: webbrowser-app
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
Title: webbrowser-app crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Till Kamppeter (till-kamppeter)]

Computer is a Lenovo Thinkpad Twist convertible operated with its touch screen.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1194248, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.