Core dump

[Spr Base]

latest snap on Ubuntu LTS
ver : 84.0.4147.89
https://bugs.chromium.org/p/chromium/issues/detail?id=1106509#c2

Can you add debug symbols for libs? I'd be happy to provide a backtrace.

note, I am running with GPU disabled!

There are various SIGTRAP, SIGSEGV core dumps I can easily reproduce

Run this 50 times

chromium-browser --no-sandbox --incognito --virtual-time-budget=5000 --disable-gpu --headless --print-to-pdf=a.pdf http://www.chimpazee.jp >> log.log 2>&1

other sites easy to reproduce if you run it 50 times

Sri-Langka.com
newdress.it
cwalkerart.net

What went wrong?
Failed to open /dev/null
[0716/091926.883693:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 1 time(s)
[0716/091926.889564:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 2 time(s)
[0716/091926.893577:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 3 time(s)
[0716/091926.894491:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 4 time(s)
[0716/091926.908258:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 5 time(s)
[0716/091926.910687:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 6 time(s)
[0716/091926.910721:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap

other core dumps from this release

Chrome_IOThread_S5_1594714909.core
Chrome_IOThread_S5_1594716342.core
Chrome_IOThread_S5_1594716369.core
Chrome_IOThread_S5_1594716698.core
Chrome_IOThread_S5_1594719025.core
Chrome_IOThread_S5_1594719158.core
Chrome_IOThread_S5_1594719721.core
Chrome_IOThread_S5_1594720056.core
Chrome_IOThread_S5_1594720555.core
Chrome_IOThread_S5_1594720727.core
Chrome_IOThread_S5_1594723143.core
Chrome_IOThread_S5_1594723555.core
Chrome_IOThread_S5_1594724765.core
Chrome_IOThread_S5_1594726735.core
chrome_S5_1594713852.core
chrome_S5_1594714094.core
chrome_S5_1594715092.core
chrome_S5_1594715446.core
chrome_S5_1594716376.core
chrome_S5_1594717583.core
chrome_S5_1594718113.core
chrome_S5_1594719128.core
chrome_S5_1594719384.core
chrome_S5_1594721440.core
chrome_S5_1594721535.core
chrome_S5_1594722795.core
chrome_S5_1594722978.core
chrome_S5_1594723249.core
chrome_S5_1594724206.core
chrome_S5_1594724258.core
chrome_S5_1594724538.core
chrome_S5_1594724988.core
chrome_S5_1594725002.core
chrome_S5_1594726378.core
chrome_S6_1594713950.core
chrome_S6_1594714908.core
chrome_S6_1594716342.core
chrome_S6_1594716368.core
chrome_S6_1594716697.core
chrome_S6_1594717712.core
chrome_S6_1594719024.core
chrome_S6_1594719157.core
chrome_S6_1594719720.core
chrome_S6_1594720055.core
chrome_S6_1594720554.core
chrome_S6_1594720726.core
chrome_S6_1594720810.core
chrome_S6_1594721013.core
chrome_S6_1594722356.core
chrome_S6_1594723142.core
chrome_S6_1594723554.core
chrome_S6_1594724764.core
chrome_S6_1594726734.core
ThreadPoolForeg_S5_1594714202.core
ThreadPoolForeg_S5_1594714760.core
ThreadPoolForeg_S5_1594717626.core
ThreadPoolForeg_S5_1594720170.core
ThreadPoolForeg_S5_1594721977.core
ThreadPoolForeg_S5_1594724067.core
ThreadPoolForeg_S5_1594726574.core
ThreadPoolServi_S5_1594714496.core
ThreadPoolServi_S5_1594718153.core
ThreadPoolServi_S5_1594718433.core
ThreadPoolServi_S5_1594718656.core
ThreadPoolServi_S5_1594721429.core
ThreadPoolServi_S5_1594721635.core
ThreadPoolServi_S5_1594721840.core
ThreadPoolServi_S5_1594723905.core
ThreadPoolServi_S5_1594726588.core
ThreadPoolServi_S5_1594726621.core

[Olivier Tilloy (osomon)]

See my comment on the upstream bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=1106509#c21

I'm unable to reproduce the crash locally, unfortunately. Let's keep this bug open, and continue the conversation on the upstream bug report, which has more useful data and input from upstream.

[Spr Base (sprbase)]

Thank you Oliver.
It's a shame snap was launched as a package format without any way to package the debug symbols.
Are there any deb packages with debug symbols that might work?

yes, I'll try run official google-chrome binary and report if it occurs.
The problem with that is I need to enable google crash reporting in the profile. My other test case uses a unique profile folder for each test run, but there's no way to initialise a profile is there default with crash reporting?

[Olivier Tilloy (osomon)]

There are chromium-browser deb packages with debug symbols (chromium-browser-dbgsym) published in the Ubuntu archive for Ubuntu 16.04 and 18.04. In newer Ubuntu releases the deb is a wrapper that installs the chromium snap.

[Spr Base (sprbase)]

Hi Oliver

Yes, I saw chromium-browser-dbgsym on those old releases, but I'm running 20.04 LTS

https://launchpad.net/ubuntu/bionic/+package/chromium-browser-dbgsym

They seem out of date, the v83 build.

Do you think they would work with 20.04LTS? Is there an easy way to compile them?

$ lsb_release -a
LSB Version: core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal

[Olivier Tilloy (osomon)]

The update to version 84 is in progress, but as I wrote earlier it's targetting 16.04 and 18.04 only. You may try to run the 18.04 packages on 20.04, but there's no guarantee it will run at all.

[Jg-jguk (jg-jguk)]

I found the deb packages, and ddeb for 83.x but couldn't get them to run.
It's a shame Ubuntu has switched to SNAP.

https://packages.ubuntu.com/bionic/amd64/chromium-browser/download

the link is rather strange, it shows "security.ubuntu.com/ubuntu" can you ask them to change that to be something more relevant to the deb download?

# dpkg -i 'chromium-browser_83.0.4103.61-0ubuntu0.18.04.1_amd64 (1).deb'
dpkg: warning: downgrading chromium-browser from 83.0.4103.97-0ubuntu0.20.04.1 to 83.0.4103.61-0ubuntu0.18.04.1
(Reading database ... 323708 files and directories currently installed.)
Preparing to unpack chromium-browser_83.0.4103.61-0ubuntu0.18.04.1_amd64 (1).deb ...
Unpacking chromium-browser (83.0.4103.61-0ubuntu0.18.04.1) over (83.0.4103.97-0ubuntu0.20.04.1) ...
dpkg: dependency problems prevent configuration of chromium-browser:
 chromium-browser depends on chromium-codecs-ffmpeg-extra (= 83.0.4103.61-0ubuntu0.18.04.1) | chromium-codecs-ffmpeg (= 83.0.4103.61-0ubuntu0.18.04.1); however:
  Package chromium-codecs-ffmpeg-extra is not installed.
  Version of chromium-codecs-ffmpeg on system is 83.0.4103.97-0ubuntu0.20.04.1.

dpkg: error processing package chromium-browser (--install):
 dependency problems - leaving unconfigured
Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu2) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.9.1-1) ...
Errors were encountered while processing:
 chromium-browser

# apt-get install chromium-codecs-ffmpeg-extra
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies.
 chromium-browser : Depends: chromium-codecs-ffmpeg-extra (= 83.0.4103.61-0ubuntu0.18.04.1) but 83.0.4103.97-0ubuntu0.20.04.1 is to be installed or
                             chromium-codecs-ffmpeg (= 83.0.4103.61-0ubuntu0.18.04.1) but 83.0.4103.97-0ubuntu0.20.04.1 is to be installed
                    Recommends: chromium-browser-l10n but it is not going to be installed
 chromium-codecs-ffmpeg : Conflicts: chromium-codecs-ffmpeg-extra but 83.0.4103.97-0ubuntu0.20.04.1 is to be installed
 chromium-codecs-ffmpeg-extra : Conflicts: chromium-codecs-ffmpeg but 83.0.4103.97-0ubuntu0.20.04.1 is to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

[Spr Base (sprbase)]

It does run actually if I also install
chromium-codecs-ffmpeg_83.0.4103.61-0ubuntu0.18.04.1_amd64.deb

[Spr Base (sprbase)]

Helo Oliver

Could Chromium be changed back to DEB please? The snap seems slow
according to articles

https://personal.jatan.space/2020/09/05/ubuntu-snap-obsession-has-snapped-me-off-of-it/

Thank you

On Thu, 30 Jul 2020 at 14:36, Olivier Tilloy <email address hidden> wrote:
>
> The update to version 84 is in progress, but as I wrote earlier it's
> targetting 16.04 and 18.04 only. You may try to run the 18.04 packages
> on 20.04, but there's no guarantee it will run at all.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1887970
>
> Title:
> Core dump
>
> Status in chromium-browser package in Ubuntu:
> New
>
> Bug description:
> latest snap on Ubuntu LTS
> ver : 84.0.4147.89
> https://bugs.chromium.org/p/chromium/issues/detail?id=1106509#c2
>
> Can you add debug symbols for libs? I'd be happy to provide a
> backtrace.
>
> note, I am running with GPU disabled!
>
> There are various SIGTRAP, SIGSEGV core dumps I can easily reproduce
>
> Run this 50 times
>
> chromium-browser --no-sandbox --incognito --virtual-time-budget=5000
> --disable-gpu --headless --print-to-pdf=a.pdf http://www.chimpazee.jp
> >> log.log 2>&1
>
> other sites easy to reproduce if you run it 50 times
>
> Sri-Langka.com
> newdress.it
> cwalkerart.net
>
>
> What went wrong?
> Failed to open /dev/null
> [0716/091926.883693:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 1 time(s)
> [0716/091926.889564:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 2 time(s)
> [0716/091926.893577:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 3 time(s)
> [0716/091926.894491:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 4 time(s)
> [0716/091926.908258:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 5 time(s)
> [0716/091926.910687:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 6 time(s)
> [0716/091926.910721:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
> Trace/breakpoint trap
>
>
>
>
> other core dumps from this release
>
> Chrome_IOThread_S5_1594714909.core
> Chrome_IOThread_S5_1594716342.core
> Chrome_IOThread_S5_1594716369.core
> Chrome_IOThread_S5_1594716698.core
> Chrome_IOThread_S5_1594719025.core
> Chrome_IOThread_S5_1594719158.core
> Chrome_IOThread_S5_1594719721.core
> Chrome_IOThread_S5_1594720056.core
> Chrome_IOThread_S5_1594720555.core
> Chrome_IOThread_S5_1594720727.core
> Chrome_IOThread_S5_1594723143.core
> Chrome_IOThread_S5_1594723555.core
> Chrome_IOThread_S5_1594724765.core
> Chrome_IOThread_S5_1594726735.core
> chrome_S5_1594713852.core
> chrome_S5_1594714094.core
> chrome_S5_1594715092.core
> chrome_S5_1594715446.core
> chrome_S5_1594716376.core
> chrome_S5_1594717583.core
> chrome_S5_1594718113.core
> chrome_S5_1594719128.core
> chrome_S5_1594719384.core
> chrome_S5_1594721440.core
> chrome_S5_1594721535.core
> chrome_S5_1594722795.core
> chrome_S5_1594722978.core
> chrome_S5_1594723249.core
> chrome_S5_1594724206.core
> chrome_S5_1594724258.core
> ...