Chromium uses ~100% of all cores, locks up, and does not exit correctly

Please open a Terminal and run

apport-collect 1642413

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

I can't tell. Does "ongoing" mean you tried with "--disable-gpu" and/or "--temp-profile"?

Is it near the time of the IO error on some "sr" device? Probably a CD-ROM.

[ 2303.773855] blk_update_request: I/O error, dev sr0, sector 108

Also, when it happens, what is the state of the chromium processes in "ps xuwww"? Please paste a few lines from the earliest processes.

I tried --disable-gpu, no difference

--temp-profile won't be an option for a number of reasons:

1: since I need the browser for work. i need my bookmarks, passwords, etc all synced and running
2: the error occurs randomly, so causing it to happen is impossible... it might take 5 minutes, it might take 5 hours

"Also, when it happens, what is the state of the chromium processes in "ps xuwww"? Please paste a few lines from the earliest processes."

sorry not sure what your asking me to do here, eli5

Is it near the time of the IO error on some "sr" device? Probably a CD-ROM.

[ 2303.773855] blk_update_request: I/O error, dev sr0, sector 108

there is nothing in the cd drive, and using it doesn't trigger the issue

I think you will find this image pretty enlightening, I can pretty consistently cause this lockup with the paypal virtual terminal(paypal.com/vt), although that is not the only website that has caused the lockup:

calexil, that graphical output doesn't tell me enough. Please open a
terminal and run

$ ps xfuwww |grep -C 1 chromium

and paste the result.

On Wed, Dec 21, 2016 at 7:16 PM, calexil <email address hidden> wrote:

> I think you will find this image pretty enlightening, I can pretty
> consistently cause this lockup with the paypal virtual
> terminal(paypal.com/vt), although that is not the only website that has
> caused the lockup:
>
>
> ** Attachment added: "chromium task manager...no memory used?"
> https://bugs.launchpad.net/ubuntu/+source/chromium-
> browser/+bug/1642413/+attachment/4794997/+files/
> Screenshot%20at%202016-12-21%2019-11-59.png
>
> --
> You received this bug notification because you are a member of Chromium
> team, which is subscribed to chromium-browser in Ubuntu.
> https://bugs.launchpad.net/bugs/1642413
>
> Title:
> Chromium uses ~100% of all cores, locks up, and does not exit
> correctly
>
> Status in chromium-browser package in Ubuntu:
> Incomplete
>
> Bug description:
> whether or not extensions are enabled, after an indeterminate amount
> of time chromium locks up(tabs are still rendered but browser cannot
> create new tabs, or navigate in existing ones) and the main process
> begins using 200-270% of my three cores, chrome task manager shows
> that no tab is using any memory and when chromium is exited the main
> thread does not quit and must be killed.
>
> I have reinstalled, disabled extensions/plugins, etc... nothing seems
> to remedy this issue.
>
> I memtested my memory and it was fine.
>
>
> It started happening october 2016
> ---
> ApportVersion: 2.20.1-0ubuntu2.4
> Architecture: amd64
> CrashDB: ubuntu
> CurrentDesktop: MATE
> DRM.card0-HDMI-A-1:
> enabled: enabled
> dpms: On
> status: connected
> edid-base64: AP///////wAi8A4mAAAAACANAQOAIht46gyVolZ
> MliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAeAAA
> A/QA4TB5TDgAKICAgICAgAAAA/ABocCBMMTczMAogICAgAAAA/wBDTlAzMzJTMFJICiAgALo=
> modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624
> 800x600 800x600 800x600 640x480 640x480 640x480 720x400
> DRM.card0-VGA-1:
> enabled: enabled
> dpms: On
> status: connected
> edid-base64: AP///////wA6kwcAAQAAAAoRAQMIKxt4CrU0pVZ
> KmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAYAAA
> A/gAKICAgICAgICAgICAgAAAA/ABNQVctU0VSSUFMCiAgAAAA/wAKICAgICAgICAgICAgAHk=
> modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768
> 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480
> 720x400
> Desktop-Session:
> 'mate'
> '/etc/xdg/xdg-mate:/etc/xdg'
> '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/'
> DistroRelease: Linux 18.1
> Env:
> 'None'
> 'None'
> InstallationDate: Installed on 2016-07-13 (159 days ago)
> InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
> Load-Avg-1min: 3.87
> Load-Processes-Running-Percent: 0.7%
> MachineType: MSI MS-7786
> Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin:
> Ubuntu]
> PackageArchitecture: amd64
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_...

Chad, should I run that when the lockup occurs, or does it not matter?

regardless here are the outputs:

When the issue is not occurring: http://dpaste.com/1ZTB6K5

and here it is when the issue IS occurring: http://dpaste.com/1BP57TZ

I feel like this issue is almost exclusively caused by paypal virtual terminal

paypal.com/vt

I can now verify that this is not a memory issue, I bought some replacement ram and the problem persists

now the lockup is happening regardless of whether or not I go to virtual terminal.

someone pls help, I don't know what to do here

As noted in IRC, paste full process list when it's happening, since none of the chromium processes in the "grep" list are misbehaving.

$ ps axfwww

And get the end of dmesg

$ dmesg |tail -n 50

Also, the vm swappiness might already be set to "10". It happened at default 60 at least once.

ps axfwww
http://dpaste.com/3RXRJBD

dmesg |tail -n 50
http://dpaste.com/1RW1DYH

ps axfuww
http://dpaste.com/1Z7642A

this is WHILE the lockup is occurring, probably the most useful piece of info here

grep flags /proc/cpuinfo

http://dpaste.com/13GJZHH

grep flags /proc/cpuinfo

from an unaffected machine with the same hardware

http://dpaste.com/0THCEEE

This also happens on google chrome browser

ongoing

here is a gdb log of the browser before lockup and during(towards the end):

http://dpaste.com/3M4JSV9

I can now confirm this issue is almost exclusively caused by the paypal virtual terminal

I have submitted a report to paypal, but if both ends are working on a fix it will be solved faster.

so, there's that

This is now happening regardless if vt is used, but is able to be triggered consistently by doing so

Someone pls help me

I just confirmed that the lockup does not replicate with --temp-profile

whatever that means, I do not know

@Chad Miller (cmiller)

I just confirmed that the lockup does not replicate with --temp-profile

This is now happening regardless if vt is used, but is able to be triggered consistently by doing so

any progress here? @cmiller