Segfault on VMap Extraction

[merek]

Hi All,

I am trying to set up MaNGOS One, but am having issues with generating the vmaps. This is running on an Ubuntu 20 LTS machine. I included what I thought were the relevant logs. Any thoughts as to what the issue would be would be greatly appreciated.

 

Thanks!

 

 Processing Map 566 (NetherstormBG)
[################################################################]
 Processing Map 568 (ZulAman)
[################################################################]
 Processing Map 572 (PVPLordaeron)
[################################################################]
 Processing Map 580 (SunwellPlateau)
[################################################################]
Error opening WDT file World\Maps\Transport176244\Transport176244.wdt
Error opening WDT file World\Maps\Transport176231\Transport176231.wdt
 Processing Map 585 (Sunwell5ManFix)
[################################################################]
Error opening WDT file World\Maps\Transport181645\Transport181645.wdt
Error opening WDT file World\Maps\Transport177233\Transport177233.wdt
Error opening WDT file World\Maps\Transport176310\Transport176310.wdt
Error opening WDT file World\Maps\Transport175080\Transport175080.wdt
Error opening WDT file World\Maps\Transport176495\Transport176495.wdt
Error opening WDT file World\Maps\Transport164871\Transport164871.wdt
Error opening WDT file World\Maps\Transport20808\Transport20808.wdt
 Processing Map 598 (Sunwell5Man)
[################################################################]

Extracting GameObject models...
 Extracting world\wmo\transports\zeppelin\transport_zeppelin.wmo
Can't open world\wmo\transports\zeppelin\transport_zeppelin.wmo, size = 0!
 No such file world\wmo\transports\zeppelin\transport_zeppelin.wmo.
Couldn't open RootWmo!!!
 Extracting <empty>\kl_onyxiaslair.wmo
Error opening WMO file <empty>\kl_onyxiaslair.wmo
Error opening WMO Root <empty>\kl_onyxiaslair.wmo
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted (core dumped)

 

This is the backtrace:

Extracting GameObject models...
 Extracting world\wmo\transports\zeppelin\transport_zeppelin.wmo
Can't open world\wmo\transports\zeppelin\transport_zeppelin.wmo, size = 0!
 No such file world\wmo\transports\zeppelin\transport_zeppelin.wmo.
Couldn't open RootWmo!!!
 Extracting <empty>\kl_onyxiaslair.wmo
Error opening WMO file <empty>\kl_onyxiaslair.wmo
Error opening WMO Root <empty>\kl_onyxiaslair.wmo
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007ffff7a78859 in __GI_abort () at abort.c:79
#2  0x00007ffff7e4d951 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x00007ffff7e5947c in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x00007ffff7e594e7 in std::terminate() () from /lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x00007ffff7e59799 in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x00007ffff7e4d562 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x0000555555570914 in ?? ()
#8  0x0000000000000000 in ?? ()

 

 

 

[Talendrys]

Hello,

How much RAM do you have ?

[merek]

4GB. Does this need more?

[Talendrys]

Not sure though.. I know Classic raised until 2Gb on my computer. Dunno about BC.

[Olion]

I assume that you have good (i.e. not broken) client files. Then you could try to do the extraction under Windows to ensure the file names are case insensitive. The same can be achieved under Linux at a FAT32 filesystem. I had an issue once (with a Camera file though) of capsed/not capsed file name.

Edited February 12, 2021 by Olion

[Thomas Farvour]

I ran into this problem with the Zero (non-BC) client files. `std::bad_alloc` is a general libstdc++ error that indicates the pointer tried to allocate new[] beyond usable system memory. Turns out I was using a VM that had only 2GB allocated to it (!) so I upped it to 4GB and it succeeded. I would check to make sure something else on your system isn't hogging more available memory and try. I don't know what the bare minimum is but apparently 2GB is definitely not enough.

Edited May 4, 2021 by Thomas Farvour