chromium-browser crashes on 4K system

Bug #1854995 reported by John Shakespeare
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-435 (Ubuntu)
New
Undecided
Unassigned

Bug Description

There is a bug which affects chromium-browser intermittently (it also affects the firefox browser, but not in necessarily the same way). It does not affect NFS (I use it), and is explicit to those two browsers. Opera browser or vivaldi browser have not been checked for the bug.

shakespeare@RYZEN:~$ uname -r
5.0.0-37-generic

shakespeare@RYZEN:~$ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: chromium-browser 78.0.3904.108-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Dec 3 22:12:30 2019
Desktop-Session:
 'xubuntu'
 '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
 '/usr/share/xfce4:/usr/share/xubuntu:/home/shakespeare/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
DetectedPlugins:

Env:
 'None'
 'None'
InstallationDate: Installed on 2019-09-25 (69 days ago)
InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Load-Avg-1min: 0.20
Load-Processes-Running-Percent: 0.1%
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/06/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3805
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX B350-F GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.default.chromium-browser: [deleted]

Revision history for this message
John Shakespeare (shakespeare1) wrote :
Revision history for this message
Olivier Tilloy (osomon) wrote :

If chromium crashes, there should be crash files for it under /var/crash.
Can you confirm? (please share the output of `ls -l /var/crash/`).

Changed in chromium-browser (Ubuntu):
status: New → Incomplete
Revision history for this message
John Shakespeare (shakespeare1) wrote : Re: [Bug 1854995] Re: chromium-browser crashes on 4K system

Hi Olivier,

The file _usr_bin_software-properties-gtk.0.crash should be examined
first, as I believe it to be the root cause of the crash. It's only 83
KB. There was also an excessively large 115 MB chromium crash log file
called _usr_lib_chromium-browser_chromium-browser.1000.crash. Are you
able to take such files?

Best Regards,
John.

On 10.12.2019 18.25, Olivier Tilloy wrote:
> If chromium crashes, there should be crash files for it under /var/crash.
> Can you confirm? (please share the output of `ls -l /var/crash/`).
>
> ** 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
Revision history for this message
Olivier Tilloy (osomon) wrote :

Sorry for the lack of feedback John…

The software-properties-gtk crash file is unrelated, but you might want to report it by running "apport software-properties".

Can you please share the chromium crash file? (either attach it to the bug if Launchpad lets you, or share it with another file sharing mechanism).

Thanks!

Changed in chromium-browser (Ubuntu):
status: Expired → New
Revision history for this message
John Shakespeare (shakespeare1) wrote :

Hi Olivier,

I have determined that it is a bug in the display driver.
How do I get the display driver to output something?
It gives no output even if
enabled=1
in /etc/default/apport.

Best Regards,
John.

On 21.2.2020 11.49, Olivier Tilloy wrote:
> Sorry for the lack of feedback John…
>
> The software-properties-gtk crash file is unrelated, but you might want
> to report it by running "apport software-properties".
>
> Can you please share the chromium crash file? (either attach it to the
> bug if Launchpad lets you, or share it with another file sharing
> mechanism).
>
> Thanks!
>
> ** Changed in: chromium-browser (Ubuntu)
> Status: Expired => New
>

Revision history for this message
Olivier Tilloy (osomon) wrote :

This bug should probably be re-targetted at the nvidia drivers package. I'm tentatively re-targetting to nvidia-graphics-drivers-435.

affects: chromium-browser (Ubuntu) → nvidia-graphics-drivers-435 (Ubuntu)
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.