EpicLPer, posted Wed Oct 10, 2018 9:02 pm (39385)

---

Got the same problem just now and it's due to QuickBMS completely filling up all RAM it can take as a 32bit application and maxing out at 2.058.504 K (on a second attempt it maxed at 2.104.396 K)

Code:

  003b87d0 9704       chara/pc/pc51_kuribo/motion/pc51_jump00a.fskb
  003b9f20 1376       chara/pc/pc51_kuribo/motion/pc51_jump00a.ftsb
  003ba100 1160       chara/pc/pc51_kuribo/motion/pc51_jump00a.fvbb
  003ba2c0 6944       chara/pc/pc51_kuribo/motion/pc51_jump00b.fskb
  003bb050 968        chara/pc/pc51_kuribo/motion/pc51_jump00b.ftsb

- error in src\extra\xalloc.c line 618: xdbg_malloc()

Error: memory allocation problem
       No such file or directory

press ENTER to quit

Here's a link to all the buffered lines from the CMD after the crash occured: https://pastebin.com/MDAsDDqU

Hm, wonder if a 64bit compile of QuickBMS would be nice for such a thing. So it indeed is a memory allocation problem

aluigi, posted Thu Oct 11, 2018 7:07 am (39398)

---

I don't see anything wrong in the log, for example there are no big fields like >= 0x1???????. It may be a different type of issue that must be fixed.
Can you provide the archive?

aluigi, posted Thu Oct 11, 2018 12:09 pm (39405)

---

ok I think I can do the test even without other samples because there is clearly a memory leak tested with bdr001.nxonnx32.bea.
Investigating...

aluigi, posted Thu Oct 11, 2018 4:30 pm (39419)

---

The source code in the CMD_Set_func function was really a mess and it will be better in quickbms 0.9.1 (fixed just now in my beta).
Thanks for the feedback.