leaks ahoy #1673
Comments
Buginator uploaded file |
Buginator commented Fixed all but stack, event, and I think that is it... |
Buginator uploaded file |
Buginator commented (In [10255]) Fix mem leaks concerning screenshots 2.3: [10249] refs #1673 |
Buginator commented (In [10257]) Fix memleak in stars 2.3: [10245] refs #1673 |
svnsync commented (In [10258]) Fix memleak in stats, and get rid of code that was causing dangling pointers. 2.3: [10246] refs #1673 |
Buginator commented (In [10259]) Fix mem leaks concerning apCompLists 2.3: [10247] refs #1673 |
Buginator commented (In [10260]) Fix mem leaks concerning Visibility 2.3: [10248] refs #1673 |
Buginator commented (In [10261]) Add new routines for MSVC that allows us to toggle the allocation tracking. Currently, it is only used in debug builds for strdup(). This was necessary to prevent reporting of tons of 'memory leaks' caused by strdup(). Mostly caused by all the parsers lack of cleaning up after themselves. Sample of what it does is shown. When we don't toggle the allocator, then it is added to the Normal Blocks. If we do toggle the allocator, then it is added to the CRT Blocks. 0 bytes in 0 Free Blocks. 2.3: [10250] refs #1673 |
Buginator commented (In [10262]) Cleanup main so we only have 1 atexit() call for our system shutdown routine, instead of hiding multiple shutdown routines using atexit() for each. Currently, we have 1 atexit for our main shutdown routine, and 1 atexit call for the exception handler. Fix mem leak for mod list. Also dump allocator stats for MSVC people 2.3: [10251] refs #1673 |
Git SVN Gateway <gateway@...> commented (In Warzone2100/warzone2100@90326fc) Fix mem leaks concerning screenshots 2.3: [10249] refs #1673 git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@10255 4a71c877-e1ca-e34f-864e-861f7616d084 |
Git SVN Gateway <gateway@...> commented (In Warzone2100/warzone2100@7019910) Fix mem leaks concerning apCompLists 2.3: [10247] refs #1673 git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@10259 4a71c877-e1ca-e34f-864e-861f7616d084 |
Zarel commented status? |
Buginator commented in limbo, since pumpkin does lots of pointer swapping for levels, and it is a mess. |
Git SVN Gateway <gateway@...> commented In Warzone2100/warzone2100@90326fc:
|
Git SVN Gateway <gateway@...> commented In Warzone2100/warzone2100@d1cd675:
|
Git SVN Gateway <gateway@...> commented In Warzone2100/warzone2100@e9f3105:
|
Git SVN Gateway <gateway@...> commented In Warzone2100/warzone2100@7019910:
|
Git SVN Gateway <gateway@...> commented In Warzone2100/warzone2100@01fee22:
|
Git SVN Gateway <gateway@...> commented In Warzone2100/warzone2100@584c4f1:
|
Git SVN Gateway <gateway@...> commented In Warzone2100/warzone2100@19696a3:
|
vexed changed status from |
vexed changed resolution from `` to |
resolution_closed
type_bug
| by BuginatorFor some crazy reason, someone thought it would be nice to nuke pointers in the 'init' stage, and not what the pointer was pointing to. This caused memory leaks.
Note, I really think we should go back to using memory pools for the blasted parser crapola, and maybe even the game state.
I believe this is part of the reason why savegames are getting 'invalid' data in them.
Fix memleak for mod_list.
Fix memleak for stars.
Fix memleak for apCompLists. (the /* ... */ stuff will be gone on commit.)
Fix memleak for ALLOC_STATS macro.
in systemShutdown(), gonna move freeComponentLists() & statsShutDown()to a better place...
and sill got to fix leaks for events (didn't have time to fix)
and visibility (didn't have time to fix)
Issue migrated from trac:1673 at 2022-04-15 21:12:28 -0700
The text was updated successfully, but these errors were encountered: