`BlockFilterIndexSync` benchmark runtime failure #34556

On NetBSD 10.1, from https://github.com/hebasto/bitcoin-core-nightly/actions/runs/21892939332/job/63202716004:

22/457 - tool_bench_sanity_check.py --bench=BlockFilterIndexSync failed, Duration: 1 s

stdout:
2026-02-11T05:17:28.338054Z TestFramework (INFO): PRNG seed is: 4354116727530332520
2026-02-11T05:17:28.339313Z TestFramework (INFO): Initializing test directory /home/runner/work/bitcoin-core-nightly/bitcoin-core-nightly/test_runner_₿_🏃_20260211_051724/tool_bench_sanity_check_430
2026-02-11T05:17:28.339571Z TestFramework (INFO): Starting: /home/runner/work/bitcoin-core-nightly/bitcoin-core-nightly/build/bin/bench_bitcoin -filter=BlockFilterIndexSync -sanity-check
Running with -sanity-check option, output is being suppressed as benchmark results will be useless.
2026-02-11T05:17:28.989444Z TestFramework (ERROR): Called Process failed with stdout='None'; stderr='None';
Traceback (most recent call last):
  File "/home/runner/work/bitcoin-core-nightly/bitcoin-core-nightly/test/functional/test_framework/test_framework.py", line 142, in main
    self.run_test()
    ~~~~~~~~~~~~~^^
  File "/home/runner/work/bitcoin-core-nightly/bitcoin-core-nightly/build/test/functional/tool_bench_sanity_check.py", line 36, in run_test
    subprocess.run(cmd, check=True)
    ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
  File "/usr/pkg/lib/python3.13/subprocess.py", line 577, in run
    raise CalledProcessError(retcode, process.args,
                             output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['/home/runner/work/bitcoin-core-nightly/bitcoin-core-nightly/build/bin/bench_bitcoin', '-filter=BlockFilterIndexSync', '-sanity-check']' died with <Signals.SIGSEGV: 11>.
2026-02-11T05:17:29.052681Z TestFramework (INFO): Not stopping nodes as test failed. The dangling processes will be cleaned up later.
2026-02-11T05:17:29.053385Z TestFramework (WARNING): Not cleaning up dir /home/runner/work/bitcoin-core-nightly/bitcoin-core-nightly/test_runner_₿_🏃_20260211_051724/tool_bench_sanity_check_430
2026-02-11T05:17:29.053918Z TestFramework (ERROR): Test failed. Test logging available at /home/runner/work/bitcoin-core-nightly/bitcoin-core-nightly/test_runner_₿_🏃_20260211_051724/tool_bench_sanity_check_430/test_framework.log
2026-02-11T05:17:29.054973Z TestFramework (ERROR): 
2026-02-11T05:17:29.055777Z TestFramework (ERROR): Hint: Call /home/runner/work/bitcoin-core-nightly/bitcoin-core-nightly/test/functional/combine_logs.py '/home/runner/work/bitcoin-core-nightly/bitcoin-core-nightly/test_runner_₿_🏃_20260211_051724/tool_bench_sanity_check_430' to consolidate all logs
2026-02-11T05:17:29.056178Z TestFramework (ERROR): 
2026-02-11T05:17:29.056490Z TestFramework (ERROR): If this failure happened unexpectedly or intermittently, please file a bug and provide a link or upload of the combined log.
2026-02-11T05:17:29.057174Z TestFramework (ERROR): https://github.com/bitcoin/bitcoin/issues
2026-02-11T05:17:29.057580Z TestFramework (ERROR): 


stderr:

Does it happen consistently? If not, maybe this is OOM?

What is the traceback? E.g from Command '['valgrind', '--tool=none', '/home/runner/work/bitcoin-core-nightly/bitcoin-core-nightly/build/bin/bench_bitcoin', '-filter=BlockFilterIndexSync', '-sanity-check'] (or equivalent)

Does it happen consistently? If not, maybe this is OOM? What is the traceback?

Any follow up here?

Does it happen consistently?

No.

If not, maybe this is OOM?

That sounds plausible.