Chromium's built-in PDF renderer crashes when rendering some files, takes unity down

Bug #1535390 reported by Olivier Tilloy on 2016-01-18
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Undecided
Unassigned

Bug Description

Chromium reliably crashes when opening some PDF files (not all of them). When it does, unity (compiz) is taken down with it and I'm taken back to the login screen. At that point logging in results in compiz seemingly crashing again, and a reboot is needed to allow logging in again.
I'm attaching a PDF file that reliably triggers the crash. Note that the file renders fine in e.g. evince.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: chromium-browser 47.0.2526.106-0ubuntu0.14.04.1.1107
ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
Uname: Linux 3.16.0-57-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jan 18 18:15:10 2016
Desktop-Session:
 'ubuntu'
 '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
 '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/'
DetectedPlugins:

EcryptfsInUse: Yes
Env:
 'None'
 'None'
InstallationDate: Installed on 2015-03-25 (299 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64+mac (20150218.1)
Load-Avg-1min: 1.15
Load-Processes-Running-Percent: 0.3%
MachineType: TOSHIBA Satellite A200
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-57-generic root=UUID=f7263bc4-72bc-441d-9b44-570c4df94a18 ro quiet splash vt.handoff=7
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/27/2007
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.70
dmi.board.name: ISKAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV1.70:bd09/27/2007:svnTOSHIBA:pnSatelliteA200:pvrPSAE3E-03K01CCE:rvnTOSHIBA:rnISKAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite A200
dmi.product.version: PSAE3E-03K01CCE
dmi.sys.vendor: TOSHIBA
gconf-keys: /desktop/gnome/applications/browser/exec = b''/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme = b''
modified.conffile..etc.default.chromium.browser: [deleted]
mtime.conffile..etc.chromium.browser.default: 2016-01-13T07:48:20.494539

Olivier Tilloy (osomon) wrote :
Chad Miller (cmiller) wrote :

Please open a terminal and run

"unity --replace --debug </dev/null &>~/Desktop/unity-gdb-lp1535390 &", reproduce the crash, and attach the new log file on your Desktop.

Changed in chromium-browser (Ubuntu):
status: New → Incomplete
Olivier Tilloy (osomon) wrote :

Attaching the log file generated per instructions above. This doesn't look very useful to me. When running `unity --replace`, I'm taken back to the login screen, is that expected?

Changed in chromium-browser (Ubuntu):
status: Incomplete → New
Olivier Tilloy (osomon) wrote :

Also attaching the chromium crash file generated when the issue happens. Note that it's the only crash file under /var/crash/.

Olivier Tilloy (osomon) wrote :

The problem persists with the latest chromium update, 48.0.2564.82-0ubuntu0.14.04.1.1108.

To post a comment you must log in.