Oxide

Crash in oxide::qt::Screen::DisplayFromQScreen() with multiple displays connected

Bug #1643976 reported by Luca Ciavatta
30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Oxide
Confirmed
Medium
Unassigned

Bug Description

1) Description: Ubuntu Zesty Zapus (development branch)
   Release: 17.04
   Linux 4.8.0-28-generic #30-Ubuntu SMP x86_64 GNU/Linux

2) webbrowser-app
   0.23+17.04.20161024.1-0ubuntu1

3) Open web-browser and navigate

4) Open web-browser and web-browser crashed

NOTE: I was in a Unity8 session.
      I a default session, web-browser works fine.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: webbrowser-app 0.23+17.04.20161024.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
Uname: Linux 4.8.0-28-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity:Unity8
Date: Tue Nov 22 18:34:21 2016
ExecutablePath: /usr/bin/webbrowser-app
InstallationDate: Installed on 2016-10-14 (39 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: webbrowser-app
Signal: 6
SourcePackage: webbrowser-app
StacktraceTop:
 __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 std::__throw_out_of_range(char const*) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
Title: webbrowser-app crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
UpgradeStatus: Upgraded to zesty on 2016-11-22 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

Revision history for this message
Luca Ciavatta (cialu) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
 __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:47
 std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:57
 __cxxabiv1::__cxa_throw (obj=obj@entry=0x55e1e432c020, tinfo=0x7fbaa32dfa98 <typeinfo for std::out_of_range>, dest=0x7fbaa300a3f0 <std::out_of_range::~out_of_range()>) at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:87
 std::__throw_out_of_range (__s=0x7fba6ec2c974 "map::at") at ../../../../../src/libstdc++-v3/src/c++11/functexcept.cc:87

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in webbrowser-app (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Olivier Tilloy (osomon) wrote : Re: webbrowser-app crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

Relevant excerpt of the stacktrace:

#6 0x00007fbaa301e2bf in std::__throw_out_of_range (__s=0x7fba6ec2c974 "map::at") at ../../../../../src/libstdc++-v3/src/c++11/functexcept.cc:87
#7 0x00007fba6aae29cc in at () at /usr/include/c++/6/bits/stl_map.h:532
#8 oxide::qt::Screen::DisplayFromQScreen () at ../../oxide/qt/core/browser/qt_screen.cc:296
#9 0x00007fba6aac3207 in oxide::qt::ContentsView::GetDisplay () at ../../oxide/qt/core/browser/oxide_qt_contents_view.cc:453
#10 0x00007fba6cf04cab in oxide::WebContentsView::GetDisplay () at ../../oxide/shared/browser/oxide_web_contents_view.cc:833
#11 0x00007fba6cf05484 in oxide::WebContentsView::ResizeCompositorViewport () at ../../oxide/shared/browser/oxide_web_contents_view.cc:199
#12 0x00007fba6cf05cee in oxide::WebContentsView::ScreenChanged () at ../../oxide/shared/browser/oxide_web_contents_view.cc:1044

affects: webbrowser-app (Ubuntu) → oxide
Olivier Tilloy (osomon)
information type: Private → Public
Revision history for this message
Michał Sawicz (saviq) wrote :

This happens in the unity8 snap on classic - unity8 crashes after wizard with the above.

Changed in oxide:
status: New → Confirmed
Revision history for this message
Olivier Tilloy (osomon) wrote :

@Michał: does this happen with only one monitor connected, or only when a secondary monitor is attached?

Revision history for this message
Luca Ciavatta (cialu) wrote :

@Olivier: in may case, it happened with laptop lid closed and secondary monitor attached. Primary monitor was turned off and I was using only the secondary.

Revision history for this message
Michał Sawicz (saviq) wrote :

@Oliver it does seem it's multi-display related indeed.

Olivier Tilloy (osomon)
summary: - webbrowser-app crashed with SIGABRT in
- __gnu_cxx::__verbose_terminate_handler()
+ Crash in oxide::qt::Screen::DisplayFromQScreen() with multiple displays
+ connected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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