Agreed.

> Unfortunately, with access to neither the Chrome source code nor the Grammarly source code, we can only guess.

Chromium source code is open. They could also certainly try different versions of Chrome to bisect when the issue has started to happen. Isn't there a chance perhaps this crash might actually be disguising a buffer overflow vulnerability as well? Typically user inputs aren't supposed to crash browser/renderer processes.