chromium-browser crashed with SIGILL in call_init()

Bug #1728189 reported by Timothy S. Rooney
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
New
Undecided
Unassigned

Bug Description

Browsing websites and this error happened. I just upgraded to 17.10 earlier in the evening. I have encountered multiple errors already. This is just the first that did not totally restart the PC.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: chromium-browser 62.0.3202.62-0ubuntu0.17.10.1380
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
DRM.card0-DVI-I-1:
 enabled: disabled
 dpms: On
 status: disconnected
 edid-base64:
 modes:
DRM.card0-HDMI-A-1:
 enabled: disabled
 dpms: On
 status: disconnected
 edid-base64:
 modes:
DRM.card0-VGA-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: AP///////wAig0CcAAAAABQLAQFoIRl66CainFdsliYQSE///oAxWUVZYVkxSoFAYUABAQEBMCqAwEFgJDBAgBMALOEQAAAeMCoAmFEAKkAwcBMALOEQAAAeAAAA/QAyoB5G/wAKICAgICAgAAAA/ABDTTYyMUYKICAgICAgAC0=
 modes: 1280x1024 1280x960 1152x864 1024x768i 1024x768 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400 720x400
Date: Fri Oct 27 22:35:26 2017
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 2017-10-27 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
InstalledPlugins:
 /usr/lib/mozilla/plugins:
   => libgnome-shell-browser-plugin.so
         (size: 18856 bytes, mtime: Thu Oct 19 01:38:31 2017)
Load-Avg-1min: 5.19
Load-Processes-Running-Percent: 0.4%
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=gpu-process\ --field-trial-handle=13922987333969195257,6403344220866299415,131072\ --use-gl=swiftshader-webgl\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x1002\ --gpu-device-id=0x68f9\ --gpu-driver-vendor=Google\ Inc.\ --gpu-driver-version=3.3.0.2\ --gpu-driver-date=2017/04/07\ --service-request-channel-token=D18F51D99C2CDDE24DFE27127C35BC74
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=48f30138-7711-4b5b-967d-052cc0a66a7c ro quiet splash vt.handoff=7
Signal: 4
SourcePackage: chromium-browser
StacktraceTop:
 ?? () from /usr/lib/chromium-browser/swiftshader/libGLESv2.so
 call_init (l=<optimized out>, argc=argc@entry=11, argv=argv@entry=0x7ffda74ad508, env=env@entry=0x7ffda74ad568) at dl-init.c:72
 call_init (env=0x7ffda74ad568, argv=0x7ffda74ad508, argc=11, l=<optimized out>) at dl-init.c:30
 _dl_init (main_map=main_map@entry=0x55ac89ed9f60, argc=11, argv=0x7ffda74ad508, env=0x7ffda74ad568) at dl-init.c:120
 dl_open_worker (a=a@entry=0x7ffda74abf90) at dl-open.c:575
Title: chromium-browser crashed with SIGILL in call_init()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 01/26/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0702
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4N68T-M-V2
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd01/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-M-V2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.default.chromium-browser: [deleted]

Revision history for this message
Timothy S. Rooney (timothysrooney) wrote :
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 #1727279, 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
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.