It's not an uncommon problem unfortunately. On Windows the OS lets programs inject DLLs into each other's address spaces, and this is actually a very common programming technique for various reasons. Apps don't expect it to happen of course, and so this is a fertile field of bugs.
Chrome does in fact attempt to block some apps from doing this because they're known to cause crashes. You can see the blacklist here:
So my guess is that Grammarly is injecting code into other processes, probably to try and gain access to their text controls so it can Grammarlyze stuff, and somewhere along the line corrupts the heap or stack in some way. The GIF aspect might be a red herring, as the crash was IIUC never reliably reproducible. Random crashes that happen sometimes but not others is strongly indicative of something being randomly corrupted.
Or it could be something else. Chrome moved to blocking third party injects by default some time ago, so maybe that's also a red herring.
Chrome does in fact attempt to block some apps from doing this because they're known to cause crashes. You can see the blacklist here:
https://source.chromium.org/chromium/chromium/src/+/main:chr...
They don't like apps doing it but you can apply for an exception:
https://sites.google.com/a/chromium.org/dev/Home/third-party...
So my guess is that Grammarly is injecting code into other processes, probably to try and gain access to their text controls so it can Grammarlyze stuff, and somewhere along the line corrupts the heap or stack in some way. The GIF aspect might be a red herring, as the crash was IIUC never reliably reproducible. Random crashes that happen sometimes but not others is strongly indicative of something being randomly corrupted.
Or it could be something else. Chrome moved to blocking third party injects by default some time ago, so maybe that's also a red herring.