It looks like it was last updated in April. I will try updating it and running the EKF replay again.
*(master)mitch:ardupilot$ git log -n1
commit c76ff32aa16cb7b7ba0ca38493c1a333f751d77f
Author: Jacob Walser <jwalser90@gmail.com>
Date: Thu Apr 19 14:53:27 2018 -0400
Sub: Do not report altitude in GLOBAL_POSITION_INT if there is no depth
sensor connected
Fix bluerobotics/ardusub#145
I’ve included the Replay.stg.txt (16 KB) file and did some snooping on where it was dying with valgrind:
...
Barometer initialised
==30502== Invalid read of size 1
==30502== at 0x453790: AP_BattMonitor::has_current(unsigned char) const (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== by 0x453C51: AP_Compass_Backend::correct_field(Vector3<float>&, unsigned char) (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== by 0x454CB2: AP_Compass_HIL::read() (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== by 0x419DA8: Compass::read() (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== by 0x40C8D7: Replay::read_sensors(char const*) (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== by 0x40CE83: Replay::loop() (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== by 0x44B614: HAL_Linux::run(int, char* const*, AP_HAL::HAL::Callbacks*) const (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== by 0x40340D: main (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== Address 0x114 is not stack'd, malloc'd or (recently) free'd
==30502==
==30502==
==30502== Process terminating with default action of signal 11 (SIGSEGV)
==30502== Access not within mapped region at address 0x114
==30502== at 0x453790: AP_BattMonitor::has_current(unsigned char) const (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== by 0x453C51: AP_Compass_Backend::correct_field(Vector3<float>&, unsigned char) (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== by 0x454CB2: AP_Compass_HIL::read() (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== by 0x419DA8: Compass::read() (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== by 0x40C8D7: Replay::read_sensors(char const*) (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== by 0x40CE83: Replay::loop() (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== by 0x44B614: HAL_Linux::run(int, char* const*, AP_HAL::HAL::Callbacks*) const (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== by 0x40340D: main (in /home/ubuntu/ardupilot/build/linux/tools/Replay)
==30502== If you believe this happened as a result of a stack
==30502== overflow in your program's main thread (unlikely but
==30502== possible), you can try to increase the size of the
==30502== main thread stack using the --main-stacksize= flag.
==30502== The main thread stack size used in this run was 8388608.
==30502==