chromium-browser crashed with signal 5 in ChromeMain()

Bug #1751829 reported by dino99 on 2018-02-26
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Medium
Unassigned

Bug Description

Was doing several things at a time (watching tv streaming, about 10 chromium tabs opened with a few news streaming too.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: chromium-browser 64.0.3282.167-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
DRM.card0-DP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: AP///////wA2g4kCAQAAAA8WAQMIXTV46qqqoFRGmCQOSEy/74CBQIHAi8CpQAEBAQEBAQEBAjqAGHE4LUBYLEUAogsyAAAeAAAA/QA4VR9LEQAKICAgICAgAAAA/ABNT04tU0lTMjg5CiAgAAAA/wBTTi0wMDAwMDAwMDEKAE4=
 modes: 1920x1080 1600x1200 1280x1024 1280x960 1360x768 1152x864 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
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:
Date: Mon Feb 26 14:42:41 2018
Desktop-Session:
 'gnome-xorg'
 '/etc/xdg/xdg-gnome-xorg:/etc/xdg/xdg-gnome-xorg:/etc/xdg'
 '/usr/share/gnome-xorg:/usr/share/gnome:/usr/share/gnome-xorg:/home/oem/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
DetectedPlugins:

EcryptfsInUse: Yes
Env:
 'None'
 'None'
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
Load-Avg-1min: 2.69
Load-Processes-Running-Percent: 0.2%
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=zygote\ --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so\ --ppapi-flash-version=28.0.0.161
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
Signal: 5
SourcePackage: chromium-browser
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ChromeMain ()
Title: chromium-browser crashed with signal 5 in ChromeMain()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 10/07/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P7.00
dmi.board.name: B150M-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
modified.conffile..etc.default.chromium-browser: [deleted]

dino99 (9d9) wrote :
information type: Private → Public

StacktraceTop:
 InitializeUserDataDir () at ../../chrome/app/chrome_main_delegate.cc:450
 PreSandboxStartup () at ../../chrome/app/chrome_main_delegate.cc:804
 Initialize () at ../../content/app/content_main_runner.cc:655
 Main () at ../../services/service_manager/embedder/main.cc:413
 content::ContentMain(content::ContentMainParams const&) () at ../../content/app/content_main.cc:19

Changed in chromium-browser (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
ahmed ezzat (zod101) on 2018-08-17
no longer affects: chromium-browser
To post a comment you must log in.