There is no lack of memory or swap. 24/7 top indicates no anomalities. Everything stable.

I used to have the task manager open for bad-tab-chasing, but on inefficient GNOME/Wayland it consumes too much cpu (same for the system monitor) It is possible that Chromium may accumulate swap that I don’t readily see. I am behind on putting Prometheus on this thing.

btw, Google helped the GNOME project to launch GNOME3. They still need help.

From what I know, it is only one profile at a time, closing everything associated with it.
- It is not equal to clicking the window X, because pop-outs close, too
- It is not equal to control+shift+Q because other profiles continue
I do not think there is a ui feature that will cause this exact behavior

This is likely a GNOME/Wayland trouble
It’s a MacBook Pro HiDPI, launching on external low dpi display

Suspecting that my scroll-back buffer wasn’t large enough, and I was missing something, I tried to launch first like this:
chromium-browser --force-device-scale-factor=0.5 2>&1 | tee --append $(date +%y%m%d)-c89-chromium-log.txt
then like this:
chromium-browser --force-device-scale-factor=0.5 2>&1 >>$(date +%y%m%d)-c89-chromium-log.txt
# no console echo

(I have to have that scaling factor, b/c when Ubuntu unbroke Chromium 55, it does no longer understand gtk3 low dpi, so everything is double-width-height)

in both cases, this makes the GNOME Terminal window terminate silently, just the way Chromium occasionally terminates one of its profiles. The computer is practically frozen for 3 min 40 s as Chromium loads 73 tabs

After a reboot, GNOME Terminal no longer crashes, and Chromium no longer blocks the computer

using this:
chromium-browser --force-device-scale-factor=0.5 2>&1 | tee --append $(date +%y%m%d)-c89-chromium-log.txt
I’ma have a log next time. On it.

GNOME Terminal was terminated by SIGTRAP, but this causes files in /var/crash, so Chromium terminated for some other reason.

It actually happened RIGHT NOW. YES

I selected the profile sector, then did my up-up-enter to launch the profiles dialog “Chromium”
As I was scrolling around in that, both windows of the profile I launched from closed. This was clearly visible b/c I had so few windows after the reboot, they were visible. There is no ui control that can cause this.

You guys have a bug!

This is also consistent, b/c I have not used the profile selector popup for very long. Before that, I do not think this was happening.

I could make it happen again.
The windows close as the Chromium dialog is loading. It is visible but not populated.

So, when launched from certain (the default?) profile, that profile is closed.
This is likely the cause, but it is not fully explained, b/c it terminates profiles other than the default, too.

Once the profiles don’t fit vertically, you must use that Manage People entry, and then, profiles are occasionally exiting.

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot