PS C:\Users\--\Documents\ServerAgent-2.2.3> .\startAgent.bat
INFO 2018-03-28 21:20:35.730 [kg.apc.p] (): Binding UDP to 4444
INFO 2018-03-28 21:20:36.731 [kg.apc.p] (): Binding TCP to 4444
INFO 2018-03-28 21:20:36.741 [kg.apc.p] (): JP@GC Agent v2.2.3 started
INFO 2018-03-28 21:20:50.628 [kg.apc.p] (): Accepting new TCP connection
INFO 2018-03-28 21:20:50.631 [kg.apc.p] (): Yep, we received the 'test' command
INFO 2018-03-28 21:20:50.632 [kg.apc.p] (): Starting measures: memory: cpu:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000010014ed4, pid=32196, tid=30984
#
# JRE version: Java(TM) SE Runtime Environment (10.0+46) (build 10+46)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (10+46, mixed mode, tiered, compressed oops, g1 gc, windows-amd64)
# Problematic frame:
# C [sigar-amd64-winnt.dll+0x14ed4]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\--\Documents\ServerAgent-2.2.3\hs_err_pid32196.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
