Error when Daa-meganizer in command line

I’m trying to meganize a daa file via the command line. But I have a problem with daa-meganizer. Here is the error message I get:

xvfb-run --auto-servernum --server-num=1 megan/tools/daa-meganizer -mdb /mnt/f/megan-map-Feb2022.db -i /mnt/f/RNA_1_W.daa
Picked up _JAVA_OPTIONS: -Xmx115G
Version   MEGAN Community Edition (version 6.24.12, built 4 Jan 2023)
Author(s) Daniel H. Huson
Copyright (C) 2022 Daniel H. Huson. This program comes with ABSOLUTELY NO WARRANTY.
Java version:
Functional classifications to use: EC, EGGNOG, GTDB, INTERPRO2GO, SEED
Loading 2,396,736
Loading ncbi.tre: 2,396,740
Loading     8,200
Loading ec.tre:     8,204
Loading    30,875
Loading eggnog.tre:    30,986
Loading   240,103
Loading gtdb.tre:   240,107
Loading    14,242
Loading interpro2go.tre:    28,907
Loading       961
Loading seed.tre:       962
Meganizing: /mnt/f/RNA_1_W.daa
Meganizing init
Annotating DAA file using FAST mode (accession database and first accession per line)
Annotating references
10% 20% 30% 40% 50% 60% 70% 80% 90% #
# A fatal error has been detected by the Java Runtime Environment:
#  SIGSEGV (0xb) at pc=0x00007fd67977b959, pid=896, tid=969
# JRE version: OpenJDK Runtime Environment ( (build
# Java VM: OpenJDK 64-Bit Server VM (, mixed mode, tiered, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C  [][thread 975 also had an error]
[thread 970 also had an error]
[thread 971 also had an error]

[timeout occurred during error reporting in step "printing problematic frame"] after 30 s.
# Core dump will be written. Default location: core.896 (may not exist)
# An error report file with more information is saved as:
# /home/hyojoeng/hs_err_pid896.log
[thread 974 also had an error][thread 972 also had an error]
[thread 973 also had an error]# [ timer expired, abort... ]
megan/tools/daa-meganizer: line 44:   896 Aborted                 (core dumped) $java $java_flags --module-path=$modulepath --add-modules=megan $options

Did I do something wrong ?

Thanks in advance

Could you please try the latest release… this might be a memory issue that I have tried to address in newer releases