chromium-browser crashed with SIGSEGV in _int_malloc()

Bug #1784838 reported by Nicolas_Raoul
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Chromium actually did not crash as far as I know, but a single tab said "Snap" when trying to load Google Maps.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: chromium-browser 67.0.3396.99-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CrashCounter: 1
DRM.card0-DP-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-DP-2:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-HDMI-A-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-HDMI-A-2:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-eDP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: AP///////wA0qaKWAAAAAP8XAQSlIhN4AhKhp1RTmSYLUFQAAAABAQEBAQEBAQEBAQEBAQEBKnZAxLBUFGAsBJEAWMEQAAAeKnZAxLBUW2EsBJEAWMEQAAAeAAAA/QAxPWBkHgEKICAgICAgAAAA/gBWVlgxNlQwMjhKMDAKAFA=
 modes: 2880x1620 2880x1620
Date: Wed Aug 1 19:55:51 2018
Desktop-Session:
 'ubuntu'
 '/etc/xdg/xdg-ubuntu:/etc/xdg'
 '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
DetectedPlugins:

Env:
 'None'
 'None'
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2018-04-29 (93 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
InstalledPlugins:
 /usr/lib/mozilla/plugins:
   => libgnome-shell-browser-plugin.so
         (size: 18856 bytes, mtime: Thu Jun 21 08:45:42 2018)
Load-Avg-1min: 2.15
Load-Processes-Running-Percent: 0.1%
MachineType: LENOVO 20CKCTO1WW
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=renderer\ --field-trial-handle=5474018128057866269,6560013605490637649,131072\ --service-pipe-token=A639C3EF39FE2CD74A8EF2B6768E4943\ --lang=en-US\ --enable-offline-auto-reload\ --enable-offline-auto-reload-visible-only\ --num-raster-threads=2\ --enable-main-frame-before-activation\ --service-request-channel-token=A639C3EF39FE2CD74A8EF2B6768E4943\ --renderer-client-id=82\ --shared-files=v8_context_snapshot_data:100,v8_natives_data:101
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7f5c39ac75bd <_int_malloc+749>: mov %r13,0x10(%rdi)
 PC (0x7f5c39ac75bd) ok
 source "%r13" ok
 destination "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 _int_malloc (av=av@entry=0x7f5c39e1ec40 <main_arena>, bytes=bytes@entry=1536) at malloc.c:3779
 __GI___libc_malloc (bytes=1536) at malloc.c:3065
 ()
 ()
 ()
Title: chromium-browser crashed with SIGSEGV in _int_malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark
dmi.bios.date: 08/20/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N11ET34W (1.10 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CKCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN11ET34W(1.10):bd08/20/2015:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T550
dmi.product.name: 20CKCTO1WW
dmi.product.version: ThinkPad T550
dmi.sys.vendor: LENOVO
modified.conffile..etc.default.chromium-browser: [deleted]

Revision history for this message
Nicolas_Raoul (nicolas-raoul) wrote :
information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Paul White (paulw2u) wrote :

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

Do you still see a problem related to the one that was reported when using Chromium 76 which is the currently supported version of Chromium? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

Changed in chromium-browser (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.]

Changed in chromium-browser (Ubuntu):
status: Incomplete → Expired
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.