When HotSpot throws any of the internal errors StackOverflow, OutOfMemory, or Linker error an internal counter is updated. These counters are currently only shown in VM.info and the hotspot error file.

```
OutOfMemory and StackOverflow Exception counts:
StackOverflowErrors=114
```

Sometimes these errors are swallowed and not reported by application code, which can cause hard to detect failures. Even if a VM.info output is taken, or the application crashes and creates an hs-err file, these counters are sometimes overlooked.

With these errors not being initialized the same way as ordinary errors, they fail to register in the JFR exception statistics. The exception statistic is based on the actual instantiation of error/exception throwables, but these errors are using pre-initialized instances. It would be beneficial to get these into the exceptions statistics. This would allow monitoring tools such as JMC to clearly categorize these thrown errors as severe issues, and suggest further diagnostic measures to take. Acting pro-actively on these kind of issues could potentially prevent crashes.