Chromium freezes

Bug #1768199 reported by DimanNe
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

After I updated to Ubuntu 18.04 I noticed that chromium interactions (scroll for example) and mouse pointer itself started to freeze for hundreds of milliseconds (0.1s - 0.2s).

So, I was constantly scrolling (in order to reproduce the bug) while running perf top, and it pointed to this function:

sudo perf top -t 1892 -d 5 --call-graph fp

  Children Self Shared Object Symbol

- 80,55% 0,00% libc-2.27.so [.] __GI___ioctl
   - 76,84% __GI___ioctl
        71,67% _nv029804rm
      - 1,12% _nv020749rm
         - 1,03% os_release_spinlock
              0,97% _raw_spin_unlock_irqrestore

- 71,69% 71,67% [kernel] [k] _nv029804rm
     71,58% 0x180000012a
        __GI___ioctl
        _nv029804rm

- 16,75% 0,00% [unknown] [k] 0x000000180000012a
     0x180000012a
   - __GI___ioctl
        15,25% _nv029804rm

- 8,67% 0,25% libc-2.27.so [.] syscall
   - 5,45% syscall
        1,89% syscall_return_via_sysret
      - 1,05% entry_SYSCALL_64_after_hwframe
         - 1,22% do_syscall_64

top command also showed that this process was eating one core.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: chromium-browser 65.0.3325.181-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: KDE
Date: Tue May 1 10:38:19 2018
Desktop-Session:
 'plasma'
 '/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
 '/usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
DetectedPlugins:

Env:
 'None'
 'None'
InstallationDate: Installed on 2017-12-16 (136 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
InstalledPlugins:

Load-Avg-1min: 1.64
Load-Processes-Running-Percent: 0.1%
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=e3723f86-9a4d-4166-960b-88262212fcc6 ro quiet splash vt.handoff=1
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to bionic on 2018-04-02 (28 days ago)
dmi.bios.date: 08/31/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0408
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z370-A
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.:bvr0408:bd08/31/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
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
DimanNe (dimanne) wrote :
description: updated
Revision history for this message
DimanNe (dimanne) wrote :

I have just noticed that dmesg has very strange info:
WARNING: kernel stack frame pointer at 00000000b2107faf in chromium-browse:1892 has bad value 00000000648ab7fa

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Revision history for this message
Olivier Tilloy (osomon) wrote :

Could you please install chrome (https://www.google.com/chrome/) and see if the problem happens there too? Thanks!

Revision history for this message
DimanNe (dimanne) wrote :

I have tried doing it, the problem have gone, it works fine. Newer Chromium (66.0.3359.139) from the Ubuntu repos also works perfectly. I suppose you can close the bug-report.

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

Thanks for the feedback. It looks like this was an upstream bug that was fixed with the release of 66 to the stable channel. Closing now.

Changed in chromium-browser (Ubuntu):
status: Confirmed → Fix Released
Olivier Tilloy (osomon)
no longer affects: chromium-browser
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.