webbrowser-app crashed in qmlscene call

Bug #1662368 reported by stinger
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
webbrowser-app (Ubuntu)
New
Undecided
Unassigned

Bug Description

looks like a QT 5.7.1 bug

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: webbrowser-app 0.23+17.04.20170110-0ubuntu1
ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
Uname: Linux 4.9.0-16-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Tue Feb 7 00:46:36 2017
ExecutablePath: /usr/bin/webbrowser-app
InstallationDate: Installed on 2016-11-06 (92 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: webbrowser-app
ProcEnviron:
 LANG=de_DE.UTF-8
 LANGUAGE=de_DE
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
Signal: 6
SourcePackage: webbrowser-app
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
 __run_exit_handlers (status=1, listp=0x7f6508fa95d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:83
 __GI_exit (status=<optimized out>) at exit.c:105
Title: webbrowser-app crashed with SIGABRT in __run_exit_handlers()
UpgradeStatus: Upgraded to zesty on 2016-11-19 (79 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

Revision history for this message
stinger (dev-t) wrote :
Revision history for this message
stinger (dev-t) wrote :

this call

#17 0x00007f650a480a32 in QOpenGLTextureGlyphCache::fillTexture(QTextureGlyphCache::Coord const&, unsigned int, QFixed) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5

ended up in

[drm] GPU HANG: ecode 6:0:0xc3b831f3, in webbrowser-app [5338], reason: Hang on render ring, action: reset
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[drm] GPU crash dump saved to /sys/class/drm/card0/error
drm/i915: Resetting chip after gpu hang

description: updated
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1560994, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
stinger (dev-t) wrote :

i dont think so.

this is on zesty with new QT 5.7.1

Revision history for this message
Olivier Tilloy (osomon) wrote :

If apport says it’s a duplicate, it’s because the stack traces are similar enough that it’s indeed the same crash, regardless of Ubuntu and Qt versions.

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.