eth-docker_consensus_1 and eth-docker_validator_1 exited with code 132

after perfomring ./ethd update both concensus and validator exits with code 132.

temp fix is git checkout 5d763b8dd9ab25394a8c1279f5752ccb8e0d9db7 and go back to version v<IP_ADDRESS>

I'd need to know your COMPOSE_FILE please to be able to look into this. Logs for the failure would also be helpful.

sorry for the delay
log is
Attaching to eth-docker_eth_1, eth-docker_validator_1, eth-docker_execution_1, eth-docker_consensus_1
eth-docker_eth_1 exited with code 0
validator_1          | Mar 09 00:19:26.810 INFO Logging to file                         path: "/var/lib/lighthouse/validators/logs/validator.log"
validator_1          | Mar 09 00:19:26.824 WARN CPU seems incompatible with optimized Lighthouse build, advice: If you get a SIGILL, please try Lighthouse portable build
validator_1          | Mar 09 00:19:26.824 INFO Lighthouse started                      version: Lighthouse/v2.1.3-c3a793f
validator_1          | Mar 09 00:19:26.824 INFO Configured for network                  name: mainnet
validator_1          | Mar 09 00:19:26.824 INFO Starting validator client               validator_dir: "/var/lib/lighthouse/validators", beacon_nodes: ["http://consensus:5052/"]
validator_1          | Mar 09 00:19:26.824 INFO Metrics HTTP server started             listen_address: <IP_ADDRESS>:5064
validator_1          | Mar 09 00:19:27.994 INFO Logging to file                         path: "/var/lib/lighthouse/validators/logs/validator.log"
validator_1          | Mar 09 00:19:28.001 WARN CPU seems incompatible with optimized Lighthouse build, advice: If you get a SIGILL, please try Lighthouse portable build
validator_1          | Mar 09 00:19:28.001 INFO Lighthouse started                      version: Lighthouse/v2.1.3-c3a793f
validator_1          | Mar 09 00:19:28.001 INFO Configured for network                  name: mainnet
validator_1          | Mar 09 00:19:28.002 INFO Starting validator client               validator_dir: "/var/lib/lighthouse/validators", beacon_nodes: ["http://consensus:5052/"]
validator_1          | Mar 09 00:19:28.002 INFO Metrics HTTP server started             listen_address: <IP_ADDRESS>:5064
validator_1          | Mar 09 00:19:29.174 INFO Logging to file                         path: "/var/lib/lighthouse/validators/logs/validator.log"
validator_1          | Mar 09 00:19:29.188 WARN CPU seems incompatible with optimized Lighthouse build, advice: If you get a SIGILL, please try Lighthouse portable build
validator_1          | Mar 09 00:19:29.188 INFO Lighthouse started                      version: Lighthouse/v2.1.3-c3a793f
validator_1          | Mar 09 00:19:29.188 INFO Configured for network                  name: mainnet
validator_1          | Mar 09 00:19:29.188 INFO Starting validator client               validator_dir: "/var/lib/lighthouse/validators", beacon_nodes: ["http://consensus:5052/"]
validator_1          | Mar 09 00:19:29.189 INFO Metrics HTTP server started             listen_address: <IP_ADDRESS>:5064
validator_1          | Mar 09 00:19:30.718 INFO Logging to file                         path: "/var/lib/lighthouse/validators/logs/validator.log"
validator_1          | Mar 09 00:19:30.732 WARN CPU seems incompatible with optimized Lighthouse build, advice: If you get a SIGILL, please try Lighthouse portable build
validator_1          | Mar 09 00:19:30.732 INFO Lighthouse started                      version: Lighthouse/v2.1.3-c3a793f
validator_1          | Mar 09 00:19:30.732 INFO Configured for network                  name: mainnet
validator_1          | Mar 09 00:19:30.733 INFO Starting validator client               validator_dir: "/var/lib/lighthouse/validators", beacon_nodes: ["http://consensus:5052/"]
validator_1          | Mar 09 00:19:30.733 INFO Metrics HTTP server started             listen_address: <IP_ADDRESS>:5064
validator_1          | Mar 09 00:19:32.522 INFO Logging to file                         path: "/var/lib/lighthouse/validators/logs/validator.log"
execution_1          | INFO [03-09|00:19:25.973] Starting pprof server                    addr=http://<IP_ADDRESS>:6060/debug/pprof
execution_1          | INFO [03-09|00:19:25.973] Starting Geth on Ethereum mainnet...
execution_1          | INFO [03-09|00:19:25.973] Bumping default cache on mainnet         provided=1024 updated=4096
execution_1          | INFO [03-09|00:19:25.973] Enabling metrics collection
execution_1          | INFO [03-09|00:19:25.977] Maximum peer count                       ETH=50 LES=0 total=50
execution_1          | INFO [03-09|00:19:25.977] Smartcard socket not found, disabling    err="stat /run/pcscd/pcscd.comm: no such file or directory"
execution_1          | INFO [03-09|00:19:25.978] Set global gas cap                       cap=50,000,000
execution_1          | INFO [03-09|00:19:25.994] Allocated trie memory caches             clean=614.00MiB dirty=1024.00MiB
execution_1          | INFO [03-09|00:19:25.994] Allocated cache and file handles         database=/var/lib/goethereum/geth/chaindata cache=2.00GiB handles=524,288
validator_1          | Mar 09 00:19:32.530 WARN CPU seems incompatible with optimized Lighthouse build, advice: If you get a SIGILL, please try Lighthouse portable build
validator_1          | Mar 09 00:19:32.530 INFO Lighthouse started                      version: Lighthouse/v2.1.3-c3a793f
validator_1          | Mar 09 00:19:32.530 INFO Configured for network                  name: mainnet
validator_1          | Mar 09 00:19:32.530 INFO Starting validator client               validator_dir: "/var/lib/lighthouse/validators", beacon_nodes: ["http://consensus:5052/"]
validator_1          | Mar 09 00:19:32.530 INFO Metrics HTTP server started             listen_address: <IP_ADDRESS>:5064
execution_1          | INFO [03-09|00:19:33.493] Opened ancient database                  database=/var/lib/goethereum/geth/chaindata/ancient readonly=false
execution_1          | INFO [03-09|00:19:33.860] Persisted trie from memory database      nodes=12356 size=1.78MiB time=67.128951ms gcnodes=0 gcsize=0.00B gctime=0s livenodes=1 livesize=0.00B
execution_1          | INFO [03-09|00:19:33.862] Initialised chain configuration          config="{ChainID: 1 Homestead: 1150000 DAO: 1920000 DAOSupport: true EIP150: 2463000 EIP155: 2675000 EIP158: 2675000 Byzantium: 4370000 Constantinople: 7280000 Petersburg: 7280000 Istanbul: 9069000, Muir Glacier: 9200000, Berlin: 12244000, London: 12965000, Arrow Glacier: 13773000, MergeFork: <nil>, Engine: ethash}"
consensus_1          | Mar 09 00:19:25.941 INFO Logging to file                         path: "/var/lib/lighthouse/beacon/logs/beacon.log"
consensus_1          | Mar 09 00:19:25.953 WARN CPU seems incompatible with optimized Lighthouse build, advice: If you get a SIGILL, please try Lighthouse portable build
consensus_1          | Mar 09 00:19:25.953 INFO Lighthouse started                      version: Lighthouse/v2.1.3-c3a793f
consensus_1          | Mar 09 00:19:25.953 INFO Configured for network                  name: mainnet
consensus_1          | Mar 09 00:19:25.953 INFO Data directory initialised              datadir: /var/lib/lighthouse
consensus_1          | Mar 09 00:19:25.954 INFO Deposit contract                        address: 0x00000000219ab540356cbb839cbe05303d7705fa, deploy_block: 11184524
consensus_1          | Mar 09 00:19:30.162 INFO Hot-Cold DB initialized                 split_state: 0x3175bf66ff13793c3b88be6b27c6465f48c6eb6239a7006cd350aa4b7061298d, split_slot: 3330016, version: 8, service: freezer_db
consensus_1          | Mar 09 00:19:30.166 INFO Starting beacon chain                   method: resume, service: beacon
consensus_1          | Mar 09 00:19:32.113 INFO Logging to file                         path: "/var/lib/lighthouse/beacon/logs/beacon.log"
consensus_1          | Mar 09 00:19:32.120 WARN CPU seems incompatible with optimized Lighthouse build, advice: If you get a SIGILL, please try Lighthouse portable build
consensus_1          | Mar 09 00:19:32.120 INFO Lighthouse started                      version: Lighthouse/v2.1.3-c3a793f
consensus_1          | Mar 09 00:19:32.120 INFO Configured for network                  name: mainnet
consensus_1          | Mar 09 00:19:32.120 INFO Data directory initialised              datadir: /var/lib/lighthouse
consensus_1          | Mar 09 00:19:32.120 INFO Deposit contract                        address: 0x00000000219ab540356cbb839cbe05303d7705fa, deploy_block: 11184524
consensus_1          | Mar 09 00:19:32.448 INFO Hot-Cold DB initialized                 split_state: 0x3175bf66ff13793c3b88be6b27c6465f48c6eb6239a7006cd350aa4b7061298d, split_slot: 3330016, version: 8, service: freezer_db
consensus_1          | Mar 09 00:19:32.454 INFO Starting beacon chain                   method: resume, service: beacon
consensus_1          | Mar 09 00:19:34.330 INFO Logging to file                         path: "/var/lib/lighthouse/beacon/logs/beacon.log"
consensus_1          | Mar 09 00:19:34.345 WARN CPU seems incompatible with optimized Lighthouse build, advice: If you get a SIGILL, please try Lighthouse portable build
consensus_1          | Mar 09 00:19:34.345 INFO Lighthouse started                      version: Lighthouse/v2.1.3-c3a793f
consensus_1          | Mar 09 00:19:34.345 INFO Configured for network                  name: mainnet
consensus_1          | Mar 09 00:19:34.345 INFO Data directory initialised              datadir: /var/lib/lighthouse
consensus_1          | Mar 09 00:19:34.345 INFO Deposit contract                        address: 0x00000000219ab540356cbb839cbe05303d7705fa, deploy_block: 11184524
consensus_1          | Mar 09 00:19:34.630 INFO Hot-Cold DB initialized                 split_state: 0x3175bf66ff13793c3b88be6b27c6465f48c6eb6239a7006cd350aa4b7061298d, split_slot: 3330016, version: 8, service: freezer_db
consensus_1          | Mar 09 00:19:34.635 INFO Starting beacon chain                   method: resume, service: beacon
execution_1          | INFO [03-09|00:19:35.084] Disk storage enabled for ethash caches   dir=/var/lib/goethereum/geth/ethash count=3
execution_1          | INFO [03-09|00:19:35.084] Disk storage enabled for ethash DAGs     dir=/home/geth/.ethash              count=2
execution_1          | INFO [03-09|00:19:35.085] Initialising Ethereum protocol           network=1 dbversion=8
eth-docker_validator_1 exited with code 132
execution_1          | INFO [03-09|00:19:36.256] Loaded most recent local header          number=14,349,334 hash=ed81b2..20cbcd td=43,306,634,090,973,331,589,591 age=44s
execution_1          | INFO [03-09|00:19:36.256] Loaded most recent local full block      number=14,349,334 hash=ed81b2..20cbcd td=43,306,634,090,973,331,589,591 age=44s
execution_1          | INFO [03-09|00:19:36.256] Loaded most recent local fast block      number=14,349,334 hash=ed81b2..20cbcd td=43,306,634,090,973,331,589,591 age=44s
execution_1          | INFO [03-09|00:19:36.256] Loaded last fast-sync pivot marker       number=13,969,419
execution_1          | WARN [03-09|00:19:36.257] Head state missing, repairing            number=14,349,334 hash=ed81b2..20cbcd snaproot=c6a88e..6d96c6
consensus_1          | Mar 09 00:19:36.622 WARN CPU seems incompatible with optimized Lighthouse build, advice: If you get a SIGILL, please try Lighthouse portable build
consensus_1          | Mar 09 00:19:36.622 INFO Lighthouse started                      version: Lighthouse/v2.1.3-c3a793f
consensus_1          | Mar 09 00:19:36.622 INFO Configured for network                  name: mainnet
consensus_1          | Mar 09 00:19:36.622 INFO Data directory initialised              datadir: /var/lib/lighthouse
consensus_1          | Mar 09 00:19:36.622 INFO Deposit contract                        address: 0x00000000219ab540356cbb839cbe05303d7705fa, deploy_block: 11184524
consensus_1          | Mar 09 00:19:36.909 INFO Hot-Cold DB initialized                 split_state: 0x3175bf66ff13793c3b88be6b27c6465f48c6eb6239a7006cd350aa4b7061298d, split_slot: 3330016, version: 8, service: freezer_db
consensus_1          | Mar 09 00:19:36.914 INFO Starting beacon chain                   method: resume, service: beacon
eth-docker_consensus_1 exited with code 132
validator_1          | Mar 09 00:19:39.402 WARN CPU seems incompatible with optimized Lighthouse build, advice: If you get a SIGILL, please try Lighthouse portable build
validator_1          | Mar 09 00:19:39.402 INFO Lighthouse started                      version: Lighthouse/v2.1.3-c3a793f
validator_1          | Mar 09 00:19:39.402 INFO Configured for network                  name: mainnet
validator_1          | Mar 09 00:19:39.403 INFO Starting validator client               validator_dir: "/var/lib/lighthouse/validators", beacon_nodes: ["http://consensus:5052/"]
validator_1          | Mar 09 00:19:39.403 INFO Metrics HTTP server started             listen_address: <IP_ADDRESS>:5064
consensus_1          | Mar 09 00:19:39.416 WARN CPU seems incompatible with optimized Lighthouse build, advice: If you get a SIGILL, please try Lighthouse portable build
consensus_1          | Mar 09 00:19:39.416 INFO Lighthouse started                      version: Lighthouse/v2.1.3-c3a793f
consensus_1          | Mar 09 00:19:39.416 INFO Configured for network                  name: mainnet
consensus_1          | Mar 09 00:19:39.416 INFO Data directory initialised              datadir: /var/lib/lighthouse
consensus_1          | Mar 09 00:19:39.416 INFO Deposit contract                        address: 0x00000000219ab540356cbb839cbe05303d7705fa, deploy_block: 11184524
consensus_1          | Mar 09 00:19:39.694 INFO Hot-Cold DB initialized                 split_state: 0x3175bf66ff13793c3b88be6b27c6465f48c6eb6239a7006cd350aa4b7061298d, split_slot: 3330016, version: 8, service: freezer_db
consensus_1          | Mar 09 00:19:39.699 INFO Starting beacon chain```

.env is

Client choice: See https://eth-docker.net/docs/Usage/ClientSetup for available options
COMPOSE_FILE=lh-base.yml:geth.yml
Execution client endpoint / chain source. This default uses the execution node container.
Nimbus requires the URL to be ws:// or wss://, e.g. ws://execution:8546
For Teku and Lighthouse, you can specify multiple endpoints separated by commas
EC_NODE=http://execution:8545
Execution client fallback nodes, for Prysm or Nimbus. Can't be empty.
EC_FALLBACK_NODE1=http://execution:8545
EC_FALLBACK_NODE2=http://execution:8545
Graffiti to use for validator
GRAFFITI=superclutch
Network to use for consensus client. If using main net, set to mainnet.
NETWORK=mainnet
Network to use for execution client. If using main net, set to mainnet.
EC_NETWORK=mainnet
Some clients suggest adjusting to higher (or lower) peer count. Adjust here, per client
PRYSM_PEER_COUNT=45
LH_PEER_COUNT=50
TEKU_PEER_COUNT=74
NIM_PEER_COUNT=160
Secure web proxy - advanced use, please see instructions
DOMAIN=example.com
<EMAIL_ADDRESS><EMAIL_ADDRESS>CF_API_TOKEN=SECRETTOKEN
AWS_PROFILE=myprofile
AWS_HOSTED_ZONE_ID=myzoneid
GRAFANA_HOST=grafana
PRYSM_HOST=prysm
EC_HOST=ec
EC_WS_HOST=ecws
CC_HOST=cc
DDNS_SUBDOMAIN=
DDNS_PROXY=true
Teku/Lighthouse/Nimbus/Lodestar rapid sync via initial state/checkpoint. For Teku, Lighthouse or Nimbus, please create an Infura
eth2/beacon project first, then replace the {projectid} and {secret} here and use one of these lines instead of the empty one
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>TEKU_RAPID_SYNC=
LH_RAPID_SYNC=
NIMBUS_RAPID_SYNC=
Set this to true to rapid sync Lodestar
LS_RAPID_SYNC=false
Consensus client address. This could be comma-separated for Lighthouse, with Infura as failover,
or could just be a remote consensus client URL for Teku, Lighthouse or Prysm "validator only" setups. Not in use for Nimbus.
CC_NODE=http://consensus:5052
Beaconcha.in API key for sending client stats. Used with lh-stats.yml or prysm-stats.yml,
source build only for Prysm as of Sept 2021.
Specify as just the API key, and give the machine name separately
BEACON_STATS_API=
BEACON_STATS_MACHINE=
P2P ports you will forward to your staking node. Adjust here if you are
going to use something other than defaults.
EC_P2P_PORT=30303
CC_P2P_PORT=9000
PRYSM_PORT=13000
PRYSM_UDP_PORT=12000
Local grafana dashboard port. Do not expose to Internet, it is insecure http
GRAFANA_PORT=3000
Local prysm web UI port. Do not expose to Internet, it is insecure http
PRYSM_WEB_PORT=7500
Secure web proxy port, 443 and 80 are great defaults
TRAEFIK_WEB_PORT=443
TRAEFIK_WEB_HTTP_PORT=80
Execution client RPC port, important when using ec-shared.yml. Also insecure, do not expose to Internet.
EC_RPC_PORT=8545
Execution client WS port, used with Nimbus. Ditto insecure, do not expose to Internet.
EC_WS_PORT=8546
SSV Node ports - note these conflict with Prysm by default
SSV_P2P_PORT=13000
SSV_P2P_PORT_UDP=12000
Geth cache size. This matters for low-memory machines such as RasPi 4, where
you may want to set it to 256. Geth will use the default if this is left blank.
#GETH_CACHE=--cache=256
GETH_CACHE=
Restart policy: Set to no if you do not want services to automatically restart
RESTART=unless-stopped
If you want debug logs, set this to debug instead of info
LOG_LEVEL=info
You can set specific version targets and choose
binary or compiled from source builds below,
via Dockerfile.binary or Dockerfile.source
These settings are not migrated when running ./ethd update
SSV
SSV_NODE_TAG=latest-ubuntu
Nimbus
NIM_SRC_BUILD_TARGET=stable
NIM_DOCKER_TAG=multiarch-latest
NIM_DOCKERFILE=Dockerfile.binary
Teku
TEKU_SRC_BUILD_TARGET=$(git describe --tags $(git rev-list --tags --max-count=1))
TEKU_DOCKER_TAG=latest
TEKU_DOCKERFILE=Dockerfile.binary
Lighthouse
LH_SRC_BUILD_TARGET=stable
LH_DOCKER_TAG=latest
LH_DOCKERFILE=Dockerfile.binary
Prysm
PRYSM_SRC_BUILD_TARGET=$(git describe --tags $(git rev-list --tags --max-count=1))
PRYSM_DOCKER_TAG=stable
PRYSM_DOCKERFILE=Dockerfile.binary
Lodestar
LS_SRC_BUILD_TARGET=$(git describe --tags $(git rev-list --tags --max-count=1))
LS_DOCKER_TAG=latest
LS_DOCKERFILE=Dockerfile.binary
Erigon
ERIGON_SRC_BUILD_TARGET=$(git describe --tags $(git rev-list --tags --max-count=1))
ERIGON_DOCKER_TAG=stable
ERIGON_DOCKERFILE=Dockerfile.binary
OpenEthereum
OE_SRC_BUILD_TARGET=$(git describe --tags $(git rev-list --tags --max-count=1))
OE_DOCKER_TAG=latest
OE_DOCKERFILE=Dockerfile.binary
Go-Ethereum aka Geth
GETH_SRC_BUILD_TARGET=$(git describe --tags $(git rev-list --tags --max-count=1))
GETH_DOCKER_TAG=stable
GETH_DOCKERFILE=Dockerfile.binary
Nethermind
NM_SRC_BUILD_TARGET=$(git describe --tags $(git rev-list --tags --max-count=1))
NM_DOCKER_TAG=latest
NM_DOCKERFILE=Dockerfile.binary
Besu
BESU_SRC_BUILD_TARGET=$(git describe --tags $(git rev-list --tags --max-count=1))
BESU_DOCKER_TAG=latest
BESU_DOCKERFILE=Dockerfile.binary
eth2.0-deposit-cli
DEPCLI_SRC_BUILD_TARGET=$(git describe --tags $(git rev-list --tags --max-count=1))
Does not (yet?) exist on Docker hub
DEPCLI_DOCKER_TAG=nonesuch
DEPCLI_LOCALDIR=./.eth
For the Node Dashboard, define a regex of mount points to ignore for the diskspace check.
NODE_EXPORTER_IGNORE_MOUNT_REGEX=^/(dev|proc|sys|run|var/lib/docker/.+)($|/)```

oh... I have a HP G7 DL580 server...it has 4x10 cores 2.4Ghz xenon cpu (old model) and 512GB Ram

it looks like the latest-modern is coming from default.env whenever i run ./ethd update   though my .env always have latest
running ./ethd update --keep-target did seem to fix the issue for me.

Okay yeah so the old CPU is the culprit here. Keep using --keep-target to stay away from the modern tag and you'll be fine.


Dispathcer.runningCallsCount🙉() method returns unpredictable value in case of work-stealing thread pool

Hi folks,
I've added a simple performance test in order to test queuedCallsCount() and runningCallsCount() Dispathcer methods.
ExecutorService executorService = Executors.newWorkStealingPool();

Dispatcher dispatcher = new Dispatcher(executorService);
dispatcher.setMaxRequests(1000);
dispatcher.setMaxRequestsPerHost(1000);

Could you please explain me why runningCallsCount() returns value bigger then maxRequests: 1000?

These limits only apply for enqueued calls, not execute. If you think it's still an issue, please provide an executable reproduction.


Importing into Eclipse

Hey StrikerX3, this looks like exactly what I need, but at the risk of asking a very dumb question, how do I import this into Eclipse to use it? I tried importing it as an existing Maven project, then adding the imports to my source and just checking for support, but the application crashes immediately every time I try running it.
I won't copy the entire log but here is the dump it gave me of the error:
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00f0f3e0, pid=7116, tid=6524
JRE version: Java(TM) SE Runtime Environment (8.0_45-b14) (build 1.8.0_45-b14)
Java VM: Java HotSpot(TM) Client VM (25.45-b02 mixed mode windows-x86 )
Problematic frame:
C  0x00f0f3e0
Failed to write core dump. 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.
---------------  T H R E A D  ---------------
Current thread (0x001ec800):  JavaThread "main" [_thread_in_native, id=6524, stack(0x00ec0000,0x00f10000)]
siginfo: ExceptionCode=0xc0000005, ExceptionInformation=0x00000008 0x00f0f3e0
Registers:
EAX=0x0000048f, EBX=0x1abda4e8, ECX=0x00000000, EDX=0x00000001
ESP=0x00f0f3b8, EBP=0x001ec940, ESI=0x0269c0c3, EDI=0x001ec800
EIP=0x00f0f3e0, EFLAGS=0x00210206
Top of Stack: (sp=0x00f0f3b8)
0x00f0f3b8:   00f0f3b8 1abda4e8 00f0f3ec 191eff68
0x00f0f3c8:   00000000 1abda4e8 00000000 00f0f3e8
0x00f0f3d8:   00f0f414 02694040 04813ec8 02698a99
0x00f0f3e8:   04846a98 00000000 04846a70 00f0f3f4
0x00f0f3f8:   1abae9f9 00f0f450 1abd9e18 00000000
0x00f0f408:   1abaecd8 00f0f3e8 00f0f450 00f0f474
0x00f0f418:   02693e60 00000000 00000000 00000000
0x00f0f428:   00000000 00000000 00000000 00000000
Instructions: (pc=0x00f0f3e0)
0x00f0f3c0:   ec f3 f0 00 68 ff 1e 19 00 00 00 00 e8 a4 bd 1a
0x00f0f3d0:   00 00 00 00 e8 f3 f0 00 14 f4 f0 00 40 40 69 02
0x00f0f3e0:   c8 3e 81 04 99 8a 69 02 98 6a 84 04 00 00 00 00
0x00f0f3f0:   70 6a 84 04 f4 f3 f0 00 f9 e9 ba 1a 50 f4 f0 00
Register to memory mapping:
EAX=0x0000048f is an unknown value
EBX={method} {0x1abda4ec} 'pollDevice' '(ILjava/nio/ByteBuffer;)I' in 'com/ivan/xinput/natives/XInputNatives'
ECX=0x00000000 is an unknown value
EDX=0x00000001 is an unknown value
ESP=0x00f0f3b8 is pointing into the stack for thread: 0x001ec800
EBP=0x001ec940 is an unknown value
ESI=0x0269c0c3 is at code_begin+627 in an Interpreter codelet
method entry point (kind = native)  [0x0269be50, 0x0269c3f0]  1440 bytes
EDI=0x001ec800 is a thread
Stack: [0x00ec0000,0x00f10000],  sp=0x00f0f3b8,  free space=316k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  0x00f0f3e0
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  com.ivan.xinput.natives.XInputNatives.pollDevice(ILjava/nio/ByteBuffer;)I+0
j  com.ivan.xinput.XInputDevice.poll()Z+9
j  com.ivan.xinput.XInputDevice.(I)V+82
j  com.ivan.xinput.XInputDevice.()V+23
v  ~StubRoutines::call_stub
j  obsessiondemo.Demo3DGraphics.start()V+182
j  Obsession.Obsession.run()V+540
j  java.lang.Thread.run()V+11
j  Obsession.Obsession.(Ljava/lang/String;IILObsession/State;)V+363
j  obsessiondemo.ObsessionDemo.()V+16
j  obsessiondemo.ObsessionDemo.main([Ljava/lang/String;)V+3
v  ~StubRoutines::call_stub
Again at the risk of sounding stupid, since I'm sure I'm just missing something simple, do you have any ideas what I might be doing wrong?

It doesn't look like you're doing anything wrong there.
I suspect there is a buffer overrun happening in the XInputNatives.pollDevice() method; the buffer allocated in Java for the XINPUT_STATE struct might not be large enough. If that's the case, then increasing the buffer size in line 70 of XInputDevice.java to 20 should fix the issue.
But then, I might be wrong there. I just printed out sizeof(XINPUT_STATE) and it returns 16 for both 32- and 64-bit platforms.
Try running the JVM with the -XX:+CreateMinidumpOnCrash VM argument. When it crashes, it should generate a largeish hs_err_pid####.mdmp along with a corresponding hs_err_pid####.log file in the project folder. Send me both files. The mdmp should compress nicely.
Another thing you can try is to compile the Native project according to the platform you're using (Release|x64 for 64-bit, for example) and copying the resulting DLLs into the appropriate folder of the Java project (src/main/resources/lib/native/win-x##), then mvn clean install to make sure you get the updated DLLs in your project. Visual Studio 2015 Community Edition works and is free.

Hey StrikerX3! Thanks for the response! Sure thing. OK I just started completely fresh, unzipped the zip into my Eclipse workspace, went to File, Import, Maven, Existing Project, Eclipse has found the "pom.xml" file, which imported a project called "xinput-device". After that I've gone to my project's properties, Java Build Path, and I've added xinput-device to my current project.
After that I've just gone to my main application and added to the start of it:
// check if XInput 1.3 is available
if (XInputDevice.isAvailable()) {
System.out.println("XInput 1.3 is available on this platform.");
}
// check if XInput 1.4 is available
if (XInputDevice14.isAvailable()) {
System.out.println("XInput 1.4 is available on this platform.");
}
I've added the imports as well to the top of the java file. I've added the -XX:+CreateMinidumpOnCrash argument to the VM and it's spat the error log and crashed with the same error as before.
Ouch, jeez, 300MB, I see now why you suggesting compressing it!
Here's a download link to the log:
https://dl.dropboxusercontent.com/u/1621976/hs_err_pid6740.zip
When I get home tonight I'll try compiling the native project like you suggest. Thankyou very much for the help StrikerX3, greatly appreciated!

Huh, strangely enough, the log and dump file tells me your code never actually touched the native library. It crashed on the boundary between Java and native code for some reason. Unfortunately I can't tell what exactly happened because there are no debug symbols for the JVM.
Try downloading the latest JDK from here and see if that helps.

Ah you're wonderful! Thankyou StrikerX3! I just tried on my laptop, downloaded the latest JDK, set it up and it worked flawlessly, I had a controller vibrate across my desk to celebrate, thankyou very much! I assume that was the problem my other computer had too, so I'll be sure to do the same when I get back home.
And thankyou for this wonderful library! Can't wait to use it in my next project.

Awesome! Glad I could help.