Re: [hatari-devel] Valgrind reported unfreed allocs at exit

[ Thread Index | Date Index | More lists.tuxfamily.org/hatari-devel Archives ]


Hi,

On 31.7.2022 2.02, Eero Tamminen wrote:
On 30.7.2022 23.29, Nicolas Pomarède wrote:
Le 30/07/2022 à 22:13, Nicolas Pomarède a écrit :
"Still reachable" means they were *not* leaked, there's still a pointer to these allocs.

By far largest amount comes from dynamic linker, then from X libs, but I noticed couple of unfreed being done directly from Hatari too:
-------------------------------------------
==9333== 2,408 bytes in 1 blocks are still reachable in loss record 2,001 of 2,016
==9333==    at 0x483877F: malloc (vg_replace_malloc.c:307)
==9333==    by 0xE6C1EA: DebugUI_Init.part.0 (debugui.c:1091)
==9333==    by 0x470347: Main_Init (main.c:776)
==9333==    by 0x470347: main (main.c:951)
-------------------------------------------
==9333== 71,680 bytes in 1 blocks are still reachable in loss record 2,015 of 2,016
==9333==    at 0x483AB65: calloc (vg_replace_malloc.c:760)
==9333==    by 0x48E73D: GemDOS_ClearAllInternalDTAs (gemdos.c:385)
==9333==    by 0x4702E8: Main_Init (main.c:750)
==9333==    by 0x4702E8: main (main.c:951)
-------------------------------------------

I'll try to look at those tomorrow, and if they can be freed, you can check whether it has impact on your reports.

I have fixes to these, but I'll wait until you've released v2.4.1 as GEMDOS HD one will need more testing to make sure it does not break anything.


	- Eero




Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/