Chrome Canary 66.0.3352.0 dies with an "Aw, Snap!" page error attempting to load the vaadin-grid 4.1.5 demos. I have seen this error with my own use of vaadin-grid beginning with Chrome Canary 66.0.3349.0. The demos (and my app) run fine in Chrome 64.
The demos page should load and the demos run.
Chrome Canary dies with
"Aw, Snap!
Something went wrong while displaying this webpage."
Example: https://vaadin.com/elements/vaadin-grid/html-examples/grid-basic-demos
Just open the demo. The app dies immediatel.
FWIW, the 5.0 beta version does the same thing. The 65.0.3325.88 Chrome Beta build has the same issue. Interestingly enough, I run Opera Beta which is based on 65.0.3325.52 and I'm fine.
Can confirm 鈥撀爐ested on macOS Chrome Canary 66.0.3353.0
Same happens also at https://cdn.vaadin.com/vaadin-grid/5.0.0-beta1/demo/ (so it鈥檚 not caused by vaadin.com).
https://cdn.vaadin.com/vaadin-grid/3.0.0/demo/ works.
As a comparison, https://cdn.vaadin.com/vaadin-date-picker/3.0.0-beta2/demo/ also works, so it鈥檚 likely to be caused directly by vaadin-grid and not by some dependency.
Just as an FYI, the Predix team is seeing "Aw, Snap!" issues in a bunch of our demos that have nothing to do with vaadin-grid. We can't had time to track down but seems like there's some deeper regression with Chrome + custom elements?
With vaadin-grid the error happens when you are extending a class with Polymer class (or something inside the iron-list).
https://github.com/vaadin/vaadin-grid/blob/master/src/vaadin-grid.html#L244
https://github.com/vaadin/vaadin-grid/blob/master/src/iron-list.html#L47
Most helpful comment
FYI x2: https://bugs.chromium.org/p/chromium/issues/detail?id=817499&can=2&start=0&num=100&q=&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=