Chromium random segfaults: error 4 in libnspr4.so
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[109127.127307] chromium-
Just random and seldom crashes.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: chromium-browser 62.0.3202.
ProcVersionSign
Uname: Linux 4.13.0-18-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: XFCE
DRM.card0-DVI-D-1:
enabled: enabled
dpms: On
status: connected
edid-base64: AP/////
modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x720 1024x768 1024x768 800x600 800x600 640x480 640x480 640x480 640x480 720x400
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-VGA-1:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
Date: Thu Dec 7 21:10:33 2017
Desktop-Session:
'xubuntu'
'/etc/
'/usr/
DetectedPlugins:
Env:
'None'
'None'
InstallationDate: Installed on 2017-08-28 (101 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Load-Avg-1min: 2.98
Load-Processes-
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to artful on 2017-09-16 (81 days ago)
dmi.bios.date: 03/10/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.
dmi.board.name: AM1I-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.
dmi.sys.vendor: ASUS
modified.
Changed in chromium-browser (Ubuntu): | |
status: | Incomplete → New |
Do you get crash reports in /var/crash ? 84-0ubuntu0. 17.10.1) also affected?
Is this a regression (i.e. were you observing the same crashes with previous versions of chromium-browser)?
Is the latest update (63.0.3239.
Do you know what triggers the crash (e.g. loading a certain type of web content, …)?