crash when starting

[BilalBoulifa]

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.

[undera]

As you see in dump "The crash happened outside the Java Virtual Machine in native code." and the native lib is "sigar-amd64-winnt.dll", which is part of SIGAR. AFAIK that lib is not maintained anymore, so I doubt this issue is fixable...

[BilalBoulifa]

not maintained anymore by you guys or who ?
because the machine is brand new one, the system is windows 10, the java is version 10, so everything is up to the latest version, is there something else old that its not maintained anymore, so it need to be updated?
there is really no solution, I mean everything has a solution for sure.

[undera]

SIGAR is the lib that we don't develop. We just used it.
I guess it's because of Java 10 having some bug. Can you try with older JAVA?

[dunham]

I encountered this issue with Java 9. Running the agent with Java 8 resolved it.

[nitinv0078]

Hi I am getting this issue on JRE12

A fatal error has been detected by the Java Runtime Environment:

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000010014ed4, pid=16372, tid=25844

JRE version: Java(TM) SE Runtime Environment (12.0.1+12) (build 12.0.1+12)
Java VM: Java HotSpot(TM) 64-Bit Server VM (12.0.1+12, mixed mode, sharing, 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

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.

--------------- S U M M A R Y ------------

Command Line: C:\PerfMon_ServerAgent-2.2.3/CMDRunner.jar --tool PerfMonAgent

Host: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz, 8 cores, 31G, Windows 10 , 64 bit Build 17763 (10.0.17763.437)
Time: Thu Jul 4 11:16:30 2019 E. Australia Standard Time elapsed time: 16 seconds (0d 0h 0m 16s)

--------------- T H R E A D ---------------

Current thread (0x000001bb2c5e6000): JavaThread "Thread-0" [_thread_in_native, id=25844, stack(0x00000038b1900000,0x00000038b1a00000)]

Stack: [0x00000038b1900000,0x00000038b1a00000], sp=0x00000038b19fe270, free space=1016k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [sigar-amd64-winnt.dll+0x14ed4]"

Is using Java 8 the only solution for it ? Is there no other way?

[MaksymRybak]

Same issue, used openjdk-shenandoah@1.8.0 to run the Server Agent.
On Windows OS, you can use Power Shell and Java Version Manager like Jabba to run the agent on whatever java version you desire.

[cnstar9988]

It is sigar 1.6.4 bug.

hyperic/sigar#141
cnstar9988/sigar@9e5dba8

[espx]

Is there a plan forward? Currently perfmon is not working on a updated windows 11. Using java 8 didn't fix this issue for me. Sigar is no longer being updated as mentioned in hyperic/sigar#141 which is a shame since hyperic/sigar#142 fixes this issue.

[undera]

I don't see what can we do without proper sigar binary release. The agent is quite tailored to SIGAR

[espx]

Clearly documenting that x64 is not supported would be nice so users don't have to hunt down bugs in dependencies. I can confirm a 32bit jvm works

[espx]

And same problem on windows server 2016 so I would consider win 64 with 64 bit jvm support completely dead

[espx]

Even better than documentation: a clear error message to the user that 64 bit jvm is not supported on windows, but 32 bit jvm can be used as workaround