lubuntu 18.10 falkon nouveau test on qutebrowser crashed with SIGSEGV in __GI_____strtoul_l_internal()

Bug #1796034 reported by Chris Guiver
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qutebrowser (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

lubuntu 18.10 daily iso - 2018-10-03 image (live system)

hardware : hp dx6120mt (mini-tower, pentium 4 dual core, 3gb, nvidia 7600gt)

In bug https://bugs.launchpad.net/ubuntu/+source/falkon/+bug/1794917 Walter (wxl) asked me to see how qutebrowser did in the same condition where falkon had issues. The result is here..

When I started cutebrowser it asked me (see screenshot me a question & warned me of issues with nouveau), I tried "FORCE SOFTWARE RENDERING" - maybe this bug-report is the fault of the person sitting at my keyboard! It may hopefully provide more clues as to the aforementioned 1794917 bug anyway.

For the record - qutebrowser was fine going to launchpad, google & a few tested sites. I then went to youtube.com (crash), then to plus.google.com (crash). Assuming the second crash overwrote the first crash file, this is the crash report I manually submitted (ubuntu-bug) from either of those two sites (plus.google.com if my order is correct).

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: qutebrowser 1.4.2-2
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic i686
ApportVersion: 2.20.10-0ubuntu11
Architecture: i386
CasperVersion: 1.396
CurrentDesktop: LXQt
Date: Thu Oct 4 06:42:57 2018
ExecutablePath: /usr/bin/qutebrowser
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Lubuntu 18.10 "Cosmic Cuttlefish" - Beta i386 (20181003)
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/qutebrowser --json-args {"basedir":\ null,\ "version":\ false,\ "temp_settings":\ [],\ "session":\ null,\ "override_restore":\ true,\ "target":\ null,\ "backend":\ null,\ "enable_webengine_inspector":\ false,\ "json_args":\ null,\ "temp_basedir_restarted":\ null,\ "loglevel":\ "info",\ "logfilter":\ null,\ "loglines":\ 2000,\ "debug":\ false,\ "json_logging":\ false,\ "color":\ true,\ "force_color":\ false,\ "nowindow":\ false,\ "temp_basedir":\ false,\ "no_err_windows":\ false,\ "qt_arg":\ null,\ "qt_flag":\ null,\ "debug_flags":\ [],\ "command":\ [],\ "url":\ []}
Python3Details: /usr/bin/python3.6, Python 3.6.6+, python3-minimal, 3.6.6-1
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
SegvAnalysis:
 Segfault happened at: 0xb7db24bb <__GI_____strtoul_l_internal+27>: movl $0x0,0x4(%esp)
 PC (0xb7db24bb) ok
 source "$0x0" ok
 destination "0x4(%esp)" (0x8028eff4) in non-writable VMA region: 0x8028e000-0x8028f000 ---p None
 Stack memory exhausted (SP below stack segment)
SegvReason: writing VMA None
Signal: 11
SourcePackage: qutebrowser
StacktraceTop:
 __GI_____strtoul_l_internal (nptr=0x8028f260 "0", endptr=0x8028f120, base=10, group=0, loc=0xb7f5bc40 <_nl_global_locale>) at strtol_l.c:252
 __GI___strtoul_internal (nptr=0x8028f260 "0", endptr=0x8028f120, base=10, group=0) at strtol.c:98
 _IO_vfscanf_internal (s=<optimized out>, format=<optimized out>, argptr=<optimized out>, errp=<optimized out>) at vfscanf.c:1864
 _IO_vsscanf (string=0x90a456b "0", format=0xb7f00e1b "%hu%n:%hu%n:%hu%n", args=0x8028f7c8 "\362\367(\200\370\367(\200\364\367(\200\370\367(\200\366\367(\200\370\367(\200@\037o\266\001ը\200") at iovsscanf.c:41
 __sscanf (s=0x90a456b "0", format=0xb7f00e1b "%hu%n:%hu%n:%hu%n") at sscanf.c:32
Title: qutebrowser crashed with SIGSEGV in __GI_____strtoul_l_internal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Chris Guiver (guiverc) wrote :
Revision history for this message
Chris Guiver (guiverc) wrote :

$ sudo lshw -C video

  *-display
       description: VGA compatible controller
       product: G73 [GeForce 7600 GT]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
       configuration: driver=nouveau latency=0
       resources: irq:24 memory:f1000000-f1ffffff memory:e0000000-efffffff memory:f2000000-f2ffffff ioport:1000(size=128) memory:c0000-dffff

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

StacktraceTop:
 __GI_____strtoul_l_internal (nptr=0x8028f260 "0", endptr=0x8028f120, base=10, group=0, loc=0xb7f5bc40 <_nl_global_locale>) at strtol_l.c:252
 __GI___strtoul_internal (nptr=0x8028f260 "0", endptr=0x8028f120, base=10, group=0) at strtol.c:98
 _IO_vfscanf_internal (s=<optimized out>, format=<optimized out>, argptr=<optimized out>, errp=<optimized out>) at vfscanf.c:1864
 _IO_vsscanf (string=0x90a456b "0", format=0xb7f00e1b "%hu%n:%hu%n:%hu%n", args=0x8028f7c8 "\362\367(\200\370\367(\200\364\367(\200\370\367(\200\366\367(\200\370\367(\200@\037o\266\001\325\250\200") at iovsscanf.c:41
 __sscanf (s=0x90a456b "0", format=0xb7f00e1b "%hu%n:%hu%n:%hu%n") at sscanf.c:32

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 qutebrowser (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Chris Guiver (guiverc)
information type: Private → Public
Revision history for this message
Axel Beckert (xtaran) wrote :

This is very likely https://bugs.debian.org/910317 ("QtWebEngine in unstable is constantly crashing").

Revision history for this message
Axel Beckert (xtaran) wrote :

I assume that since https://bugs.debian.org/910317 is fixed for a long time, this issue is no more present either.

Please file a new bug report if you still can reproduce this (or seeming identical) issues in recent versions of qutebrowser, e.g. 1.14.1 or 2.0.1 and above.

Changed in qutebrowser (Ubuntu):
status: New → Fix Released
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.