grepwood/freeradical

FreeRadical is a free software game engine hoping to accurately immitate that of Fallout 2 and 1

freeradical's Issues

Memory leaks when opening FO1 master.dat

grepwood@Durandal ~/git/FreeRadical $ valgrind ./main ~/MASTER.DAT 
==10963== Memcheck, a memory error detector
==10963== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==10963== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info
==10963== Command: ./main /home/michael/MASTER.DAT
==10963== 
DatX has not been drafted yet.
File path is /home/grepwood/MASTER.DAT
Detected version: 1
==10963== Invalid write of size 1
==10963==    at 0x400C6C: AllocateFile1 (DataSize.c:94)
==10963==    by 0x400ED5: AllocateDir1 (DataSize.c:124)
==10963==    by 0x400FB0: AllocateDat1 (DataSize.c:136)
==10963==    by 0x40118C: FR_ReadDAT (DataSize.c:171)
==10963==    by 0x40133F: main (DataSize.c:215)
==10963==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==10963== 
==10963== 
==10963== Process terminating with default action of signal 11 (SIGSEGV)
==10963==  Access not within mapped region at address 0x0
==10963==    at 0x400C6C: AllocateFile1 (DataSize.c:94)
==10963==    by 0x400ED5: AllocateDir1 (DataSize.c:124)
==10963==    by 0x400FB0: AllocateDat1 (DataSize.c:136)
==10963==    by 0x40118C: FR_ReadDAT (DataSize.c:171)
==10963==    by 0x40133F: main (DataSize.c:215)
==10963==  If you believe this happened as a result of a stack
==10963==  overflow in your program's main thread (unlikely but
==10963==  possible), you can try to increase the size of the
==10963==  main thread stack using the --main-stacksize= flag.
==10963==  The main thread stack size used in this run was 8388608.
==10963== 
==10963== HEAP SUMMARY:
==10963==     in use at exit: 2,666 bytes in 4 blocks
==10963==   total heap usage: 6 allocs, 2 frees, 3,802 bytes allocated
==10963== 
==10963== LEAK SUMMARY:
==10963==    definitely lost: 0 bytes in 0 blocks
==10963==    indirectly lost: 0 bytes in 0 blocks
==10963==      possibly lost: 0 bytes in 0 blocks
==10963==    still reachable: 2,666 bytes in 4 blocks
==10963==         suppressed: 0 bytes in 0 blocks
==10963== Rerun with --leak-check=full to see details of leaked memory
==10963== 
==10963== For counts of detected and suppressed errors, rerun with: -v
==10963== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)
Naruszenie ochrony pamięci

There's no way to play videos

So it's time to cannibalize stuff from grepwood/waave