Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 1
    Yes, I have them. If everything seems to be working fine in Chrome, then you can effectively ignore these events. When a memory allocation fails (with execute protection), the app should have some safe fallbacks. Here's a potentially better explanation from MS.
    – leeharvey1
    Commented May 20, 2022 at 11:17
  • @leeharvey1 interestingly, going off of my browser history, this only seems to happen sometimes on launch, ie before I've even attempted to do anything else eith the browser. Commented May 20, 2022 at 12:49
  • @leeharvey1 Are yours occurring only on the launching of chrome, as opposed to any other specific action? Commented May 26, 2022 at 15:36
  • No, my events don't normally occur during Chrome startups. If I had to guess, they seem more related to Chrome app updates, or background crash reporting. I have other Chromium browsers, and they're reporting too -- but not during launches.
    – leeharvey1
    Commented May 27, 2022 at 13:01
  • So same event 2 for dynamic code, chromium browsers, but not just after launch? Hmmm, I'll have to see what I am doing next time to determine it. I suppose if it's a common thing, it's probably just being done because of the way the browser is handling code, as opposed to something malicous right? Commented May 27, 2022 at 13:21