Tested in chrome # 70.0.3538.102 on Linux Debian Rodete and not able to reproduce the issue.

@lucas: Could you please try to download from URL (https://www.chromium.org/getting-involved/dev-channel) and let us know the observations of the issue and provide us with a any other information of the issue which would help us to triage the issue further.

Thanks in Advance.

Confirmed.
Both.. the new Chrome and Chromium are crashing like hell!

BTW.. What the heck dev's have done to this nice browsers?! And for what purpose? It was working super fine before the 70 version.
There was all okay in the v.69. Since this crappy update to 70.x it is now totally unusable piece of crap!

Sorry.. but I am pissed off, because my daily work is dependent on this particular browser and I can not do my duties due to this damn update.

How can I bring back the 69 version of Chromium, without the dependencies with the (in the meantime) upgraded icu?
Chromium v.69 don't work with the icu v.63.x.
Sadly if I downgrade icu to the 60 or 61 version, the many other apps stops working, like the lightdm for example.

Is there any painless method to have this one Chromium version?

Chromium: 70.0.3538.102
System: Arch
Kernel: 4.18.16-arch1-1-ARCH x86_64

BTW.. (Sorry for post under post, but I don't see here "edit" option for comments).

All those FC's problems started with this issue..

Here:
https://bbs.archlinux.org/viewtopic.php?id=241389

And here:
https://bugs.chromium.org/p/chromium/issues/detail?id=900423

Strange only is that in both browsers at once happened that same problem.

Installed dev version.  Ran just fine on the first attempt.  Got the following from the terminal window:

[19565:19565:1119/215616.411829:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.
Gkr-Message: 21:56:16.415: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
[19526:19577:1119/215616.429206:ERROR:object_proxy.cc(621)] Failed to call method: org.freedesktop.Notifications.GetCapabilities: object_path= /org/freedesktop/Notifications: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files
Gkr-Message: 21:56:42.850: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
[19526:19526:1119/215647.675912:ERROR:CONSOLE(1)] "Uncaught ReferenceError: inline is not defined", source: chrome://sync-confirmation/ (1)
[19526:19526:1119/215657.774363:ERROR:http_bridge.cc(126)] Not implemented reached in virtual void syncer::HttpBridgeFactory::OnSignalReceived()
[19526:20520:1119/215657.774608:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates

Tried closing and re-launching, crashed on launch with the following in the terminal window:
[20779:20779:1119/215825.159922:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.

Thank you for providing more feedback. Adding the requester to the cc list.

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

I managed to run the browser without the FC.

This is how I do that..

Firstly I've check if all with my sandboxing is okay. I just installed Vivaldi and Yandex-browser.. both are chromium based and both are working fine for me. They are not FC'ing at all. So.. it means there is no problem with my kernel and such things.

Then.. I do a full Chromium backup. Included all configs, profile datas etc. I mean totally all stuff related to Chromium.

Next I removed Chromium completely from my system and cleaned that what remains from it.

The next step was a full reboot and chromium installation from the system repos. It was a bit newest version than before due to meantime update in the repos to the v.70.0.3538.110.

Then I disconnected the network and started the browser without it on the "clean basis". (no plugins, no addons, no sync, no my datas etc.)

It started without any issues.

Then I closed it completely. (the best way is to restart the system to be sure that nothing hangs or works in the background), and after that I start to import my stuff into it.

Turned on sync and imported one by one my things.. but without addons and plugins.
Just a basic stuff, like my theme, favs, and so on.

If this was ready.. i fully restarted Chromium again and imported my addons but also one by one (not all at once), and now all is working fine.

It looks like the cause of those FC's was somehow changed token's datas. I don't know why, but they was different before than I have them now.

Seems that google have changed something in the account login process (this account in the browser used for data syncing, not that for the g-emails, g+ etc.).
Sadly they not inform nowhere users about such changes.

And as for the few hours I use now this new one Chromium all works okay.
Let's hope it will remains so ;)

BTW.. One important tip, before you start to experiment with some "dev" versions mentioned by rbasuvula.

Make a FULL PROFILE BACKUP!
Because if you run such browser version downloaded in the zip file, it will for 100% mess up your main, original profile!
In the other words.. before you do something, be sure you have done a backup.

Thanks for the update! Could you please help us with 16 digit crash id from chrome://crashes of the issue which would help us to triage the issue further.

Thanks you! 

@rbasuvula..
Mine sadly is empty on this newest one version, and I don't have any backups from the previous crashing one. Sorry.

I tried mcbu's method of cleaning everything out, but I must not be cleaning absolutely everything because it's only working partially.  Here's what I did and what happens:

1: Uninstall chrome.
2: Delete ~/.config/chrome
3: Reboot.
4: Re-install chrome.
5: Disconnect network.
6: Run chrome; it starts successfully.  Do not turn on sync.
7: Go into chrome settings, remove all extensions.  Exit chrome.
8: Reboot, reconnect network.
9: Run chrome.  Turn on sync; this causes several extensions to self-install.
10: Remove all extensions, exit chrome.
11: Uninstall chrome.
12: Delete ~/.config/chrome
13: Reboot.
14: Re-install chrome.
15: Disconnect network.
16: Run chrome; it starts successfully.  Do not turn on sync.
17: Go into chrome settings, check extensions.  Google docs plugin is back; remove it.  Exit chrome.
18: Reboot, reconnect network
19: Run chrome.  Turn on sync.
20: Go into chrome settings, check extensions.  Google drive plugin is back; remove it.  Exit chrome.
21: Re-launch chrome; it crashes just like it originally did.

Just for fun, I tried cleaning everything out an uninstalling yet again.  This time, I ran chrome but did not turn on sync.  I was able to successfully run and close chrome repeatedly as long as I did not turn on sync.  Encouraged by this, I logged into gmail but did not turn on sync.  Then I exited chrome and tried launching again, and got the following:

[5896:5926:1124/150256.442914:ERROR:database.cc(1828)] OptOutBlacklist sqlite error 5, errno 0: database is locked, sql: PRAGMA auto_vacuum
[5896:5926:1124/150256.443357:ERROR:database.cc(1828)] OptOutBlacklist sqlite error 5, errno 0: database is locked, sql: PRAGMA journal_mode=TRUNCATE
[5935:5935:1124/150256.461070:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process.
Gkr-Message: 15:02:56.469: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
[5896:5926:1124/150257.445729:ERROR:database.cc(1828)] OptOutBlacklist sqlite error 5, errno 0: database is locked, sql: PRAGMA cache_size=250
[5896:5926:1124/150257.445956:ERROR:database.cc(1828)] OptOutBlacklist sqlite error 5, errno 0: database is locked, sql: SELECT name FROM sqlite_master WHERE type=? AND name=? COLLATE NOCASE
[5896:5926:1124/150257.446191:ERROR:database.cc(1828)] OptOutBlacklist sqlite error 5, errno 0: database is locked, sql: CREATE TABLE IF NOT EXISTS previews_v1 (host_name VARCHAR NOT NULL, time INTEGER NOT NULL, opt_out INTEGER NOT NULL, type INTEGER NOT NULL, PRIMARY KEY(host_name, time DESC, opt_out, type))
[5896:5926:1124/150257.446365:ERROR:database.cc(1828)] OptOutBlacklist sqlite error 5, errno 0: database is locked, sql: SELECT type, version FROM enabled_previews_v1
[5896:5926:1124/150257.446525:ERROR:database.cc(1828)] OptOutBlacklist sqlite error 5, errno 0: database is locked, sql: INSERT INTO enabled_previews_v1 (type, version) VALUES  (?, ?)
[5896:5926:1124/150257.446628:ERROR:database.cc(1828)] OptOutBlacklist sqlite error 5, errno 0: database is locked, sql: SELECT host_name, time, opt_out, type FROM previews_v1 ORDER BY host_name, time DESC

So, mcbu is clearly right that there's something about google accounts which causes this crash.  I just can't figure out how to clean things out as thoroughly as he did.

Thank you for providing more feedback. Adding the requester to the cc list.

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

@lucas.. Yes.. That's exactly what will happen because the main issue: "sandbox_linux.cc(379)" will leave the browser database(s) open, because one or more browser background processes will still remain in the system as zombie ones. 

Normally Chrome/Chromium should kill all of them on exit. But in this case he does not.

So is it.. One issue entails another one and then another one, and all together they lead to the whole problem.

And..
She came to these conclusions by finding and reading this:
https://wtanaka.com/node/8132
Yeap.. I am a woman ;)
My name is Martina.

And one more idea..
I think that this sql issue can be also from the google-drive add-on.
Normally I don't use it, I don't even have it installed.
It is installed ootb with a fresh browser installation.
I always throw away all of this google-bs-crap from my browser before I do the sync.

This is the list of my extensions I use normally:
--
NooBoss : version 0_1_7_0
Magic Actions for YouTube™ : version 7_7_5_0
Chrome Web Store : version 0_2
h264ify : version 1_0_9
Nimbus Screenshot & Screen Video Recorder : version 8_7_3
DownAlbum : version 0_18_10_3
Stylus : version 1_5_0
VS Launcher : version 1_0
Videostream for Google Chromecast™ : version 2_18_905_1
Image-Toolbar : version 2_0_0_1
Search by Image (by Google) : version 1_5_2
Tampermonkey : version 4_7_44
Chameleon : version 1_8_7
Disable HTML5 Autoplay : version 0_6_2
Video Downloader professional : version 1_98_4
MyJDownloader Browser Extension : version 3_2_33
User-Agent Switcher for Google Chrome : version 1_9_3
Video Downloader PLUS : version 5_0_5
I don't care about cookies : version 2_9_3
Nano Adblocker : version 1_0_0_77
HTTPS Everywhere : version 2018_10_31
Nano Defender : version 15_0_0_75
TinEye Reverse Image Search : version 1_3_0
SearchPreview : version 5_3
New XKit : version 7_8_2
Always Clear Downloads 2 : version 2_1_3
Speed Dial 2 New tab : version 2_2_6
Social Video Downloader : version 1_0_6
Chromium Wheel Smooth Scroller : version 2_0_2
CryptoTokenExtension : version 0_9_73
SimpleExtManager : version 1_4_8
Material Downloads - Download Manager : version 3_0_0
Morpheon Dark : version 5_0
Flashcontrol : version 9_4
Extensions Update Notifier : version 3_5
F.B.(FluffBusting)Purity : version 26_1_2_0
TabCloud : version 1_17
WebRTC Network Limiter : version 0_2_1_3
KDE Connect : version 0_1_4
Alternate Tab Order : version 1_0_13
Apt-linker : version 1_3_1

@Martina,

Thank you very much for your help!

I tried the whole process over again, cleaning everything out and uninstalling all of the extensions.  Even with absolutely no extensions installed, I still get the issue.  I ran the command from the link you provided, to kill processes with sqlite databases open.  It returned this:

/home/luke/.config/google-chrome/Default/Web Data: 21656m
/home/luke/.config/google-chrome/Default/previews_opt_out.db: 21656m

If I run the command to kill these processes and then delete the 'Web Data' folder and previews_opt_out.db, chrome will launch, but then will generate new ones, so that it will crash the next time I try to launch it.  It's inconvenient, but I can use chrome by killing these processes and deleting the offending files every time I want to run it.  Any idea how I might change a setting or config file to totally disable these so that I don't have to clean them out every time?

I tried another clean install of chrome, but this time leaving in all of the default extensions, and then installing a few others that I normally use (e.g. ghostery).  After activating sync and quitting chrome, I re-launched and ran the kill script to see what it would turn up.  All it came back with were the same two: 'Web Data' and previews_opt_out.db.  Killed the scripts, deleted the files, and then was able to start chrome just fine, even with all of my extensions running.

Thanks for the update! Could you please confirm as per comment #14 can we close this issue.

Thank you!

@Lucas.. yes, it can be a sort of workaround to bring the browser to work. But this is no fix. The main (whole) problem will remains.
It seems to be an multi-issue. I mean, caused (or if I can say so.. launched) by the multiple factors.

@rbasuvula The problem is that, after some few days of working fine this bug is comes back again. So.. please do not closing the issue report but fixing this permanently :) so we can use the browser safely.