// Adding to the above comment.

Able to reproduce the issue on Mac OS 10.13.5 on the latest Canary 69.0.3466.0.

Bisect Information:
===================
Good Build: 69.0.3464.0
Bad Build : 69.0.3465.0

By running the per-revision bisect script, the below changelog URL was returned:
https://chromium-review.googlesource.com/1076809
But this seems to be irrelevant to the issue.

Hence providing manual Changelog URL from omahaproxy:

https://chromium.googlesource.com/chromium/src/+log/69.0.3464.0..69.0.3465.0?pretty=fuller&n=10000

From the above Changelog, suspecting the below change:
Reviewed-on: https://chromium-review.googlesource.com/1100086

chrisha@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner.

Removing 'ReleaseBlock-Stable' label and adding 'ReleaseBlock-Beta' as this issue is on the latest Canary. Please feel free to remove if it is not applicable.

Thanks

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/bb3988a5198d953ef6ac5e7ba6c8b6a88c984a6a

commit bb3988a5198d953ef6ac5e7ba6c8b6a88c984a6a
Author: Francois Doray <fdoray@chromium.org>
Date: Fri Jun 22 18:24:39 2018

RC: Fix invalid access when getting site engagement score in chrome://discards.

There was an invalid access when the site engagement score of a
WebContents that was never navigated was obtained in chrome://discards.
With this CL, we return 0 as the engagement score of never-navigated
WebContents, instead of doing an invalid access.

Creating a new tab or opening a link in a new tab are actions that
create a WebContents a briefly keep it in a non-navigated state.

Bug:  854497 
Change-Id: I204509b7c41445ac4b524f9a652f006189e4fcd9
Reviewed-on: https://chromium-review.googlesource.com/1111908
Reviewed-by: Sébastien Marchand <sebmarchand@chromium.org>
Commit-Queue: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569700}
[modify] https://crrev.com/bb3988a5198d953ef6ac5e7ba6c8b6a88c984a6a/chrome/browser/ui/webui/discards/discards_ui.cc

Able to reproduce this issue on Windows 10, Mac OS 10.13.5 and Ubuntu 14.04 on the build without fix 69.0.3465.0 and the issue is fixed on the latest Canary 69.0.3472.0.
Cannot observe any browser crash after following the steps mentioned in the original comment.
Attached is the screen cast for reference.

Hence adding TE verified labels as the fix is working as intended.

Thanks..

Deleted: 854497-M69.mp4 3.2 MB

	854497-M69.mp4 3.2 MB View Download