Messages

1

General / Re: 2.4.1 Memory leak with sf::Text?

« on: April 26, 2017, 08:35:07 am »

Hello, I have also find that there is a memory leak on the setOutlineThickness function.
I don't have any leaks without calling it (except the "still reachable: 115,181 bytes in 411 blocks"), but by calling it every frame I get these leak summary using valgrind.

==6109== Memcheck, a memory error detector
==6109== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==6109== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==6109== Command: ./topkek
==6109==
==6109==
==6109== HEAP SUMMARY:
==6109==     in use at exit: 8,832,001 bytes in 8,403 blocks
==6109==   total heap usage: 71,083 allocs, 62,680 frees, 597,496,658 bytes allocated
==6109==
==6109== LEAK SUMMARY:
==6109==    definitely lost: 159,840 bytes in 1,998 blocks
==6109==    indirectly lost: 8,556,726 bytes in 5,993 blocks
==6109==      possibly lost: 254 bytes in 1 blocks
==6109==    still reachable: 115,181 bytes in 411 blocks
==6109==         suppressed: 0 bytes in 0 blocks
==6109== Rerun with --leak-check=full to see details of leaked memory
==6109==
==6109== For counts of detected and suppressed errors, rerun with: -v
==6109== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)