Closed wzdev-ci closed 12 years ago
_TX uploaded file 0001-Fix-non-critical-memleak-in-NETinit-NetPlay.MOTD.patch
(1.2 KiB)
_TX uploaded file 0002-Fix-non-critical-memleak-in-initEffectsSystem-chunkL.patch
(2.3 KiB)
_TX uploaded file 0003-Fix-non-critical-memleak-in-NETinitQueue-netQueues-a.patch
(3.4 KiB)
_TX uploaded file 0004-Fix-non-critical-memleak-in-createHeader-dbgHeader.patch
(2.5 KiB)
vexed changed status from new
to closed
vexed changed resolution from ` to
duplicate`
vexed commented
Please keep these in one ticket, we have 3 tickets open for this now.
Duplicate of #3395, #3218
_TX uploaded file 0005-Fix-non-critical-memleak-in-NETinitQueue-netGameQueu.patch
(3.1 KiB)
Though kind of redundant - vexed had fixed that one already too #3395
_TX commented
Replying to Warzone2100/old-trac-import#3399 (comment:1):
Please keep these in one ticket, we have 3 tickets open for this now.
Duplicate of #3395, #3218
Oh, and I'm sorry, I thought I was supposed to open a new patch ticket (according to https://github.com/Warzone2100/warzone2100/pull/30). But oki doki, I will stop posting to this ticket then now, no problem :). You're right, it is getting, ehm, slightly confusing with four places to post comments :D.
keyword_init
keyword_memleak
keyword_startup
keyword_valgrind
resolution_duplicate
type_patch (an actual patch, not a request for one)
| by T_XCopy and Pasta from: https://github.com/Warzone2100/warzone2100/pull/30
These should fix some non critical memory leaks which were caused by memory allocated during startup but Not being properly freed during shutdown. They are shown when starting warzone2100 with "valgrind --leak-check=full" and hitting "Quit Game" right afterwards.
Refs #3395 (http://developer.wz2100.net/ticket/3395).
After those four patches, the following two valgrind errors are still left during this minimal startup phase for me:
But I can't tell yet, whether they are warzone2100's fault or external issues. For the former, looking at the QuesoGLC 0.7.2 documentation and source code as well as some printf'ing in the Warzone2100 code it looked more like a bug in the external glcDeleteContext() function which as far as I can tell is properly called from the warzone2100 side. For the latter - no idea where that comes from.
Issue migrated from trac:3399 at 2022-04-16 09:44:00 -0700