Periodic JVM appears hung

Periodically, we have gateways crashing/hanging. Version 8.0.14

Wrapper.log:

STATUS | wrapper  | 2020/12/10 14:15:37 | Pinging the JVM took 7 seconds to respond.
STATUS | wrapper  | 2020/12/10 14:16:14 | JVM appears hung: Timed out waiting for signal from JVM.  Restarting JVM.
ERROR  | wrapper  | 2020/12/10 14:16:31 | Failed to terminate the JVM, abort all restart.
ERROR  | wrapper  | 2020/12/10 14:16:32 | Failed to terminate the JVM.
STATUS | wrapper  | 2020/12/10 14:16:38 | <-- Wrapper Stopped

The PC was unresponsive so we had to power cycle it. The next line was the next entry after the previous above.

STATUS | wrapper | 2020/12/10 15:12:37 | --> Wrapper Started as Service

Just happened to me today on a server that has been running fine for years (Ignition 7.9). Also got the JVM appears hung message and Ignition never restarted. I saved the log files to look into it a bit more. I did hear that someone was running a very long report with 1 year worth of historian data and that might have caused the issue.

I have been getting similar in my wrapper.log:

INFO   | jvm 2    | 2021/05/08 20:31:06 | W [ClockDriftDetector            ] [03:31:05]: Clock drift, degraded performance, or pause-the-world detected.
INFO   | jvm 2    | 2021/05/08 20:31:06 | Max allowed deviation=1000ms, actual deviation=2885ms 
INFO   | jvm 2    | 2021/05/08 20:31:08 | W [ClockDriftDetector            ] [03:31:08]: Clock drift, degraded performance, or pause-the-world detected.
INFO   | jvm 2    | 2021/05/08 20:31:08 | Max allowed deviation=1000ms, actual deviation=1470ms 
INFO   | jvm 2    | 2021/05/08 21:52:46 | W [ClockDriftDetector            ] [04:52:46]: Clock drift, degraded performance, or pause-the-world detected.
INFO   | jvm 2    | 2021/05/08 21:52:46 | Max allowed deviation=1000ms, actual deviation=1840ms 
STATUS | wrapper  | 2021/05/08 21:57:48 | JVM appears hung: Timed out waiting for signal from JVM.  Restarting JVM.
INFO   | jvm 2    | 2021/05/08 21:57:55 | W [ClockDriftDetector            ] [04:57:54]: Clock drift, degraded performance, or pause-the-world detected.
INFO   | jvm 2    | 2021/05/08 21:57:55 | Max allowed deviation=1000ms, actual deviation=40509ms 
ERROR  | wrapper  | 2021/05/08 21:58:11 | Timed out waiting for the OS to forcibly terminate the JVM process, unable to continue.
ERROR  | wrapper  | 2021/05/08 21:58:11 |   The scheduled restart of the JVM has been cancelled.
STATUS | wrapper  | 2021/05/08 21:58:11 | <-- Wrapper Stopped
STATUS | wrapper  | 2021/05/14 09:12:00 | --> Wrapper Started as Service

Possibility for my scenario is underpowered VM provided by IT (4GB ram, Core i7-4790 CPU), hoping tech support can confirm this.