Sending valgrind logs to...

[Gilles Caulier]

Did you use the native digiKam package from your distribution ?

Which operations did you run in digiKam exactly ?

Best regards

Gilles Caulier

Le lun. 13 juil. 2026 à 13:44, Cyril Giraud <cgiraud at free.fr> a écrit :
>
> Hi Gilles,
>
> Probably yes for digikam 9.0.0 (native for UbuntuStudio 26.04):
> ==1415992== LEAK SUMMARY:
> ==1415992==    definitely lost: 9,208 bytes in 93 blocks
> ==1415992==    indirectly lost: 17,819,646 bytes in 71,055 blocks
> ==1415992==      possibly lost: 387,519,486 bytes in 44,750 blocks
> ==1415992==    still reachable: 1,377,846 bytes in 4,720 blocks
> ==1415992==                       of which reachable via heuristic:
> ==1415992==                         newarray           : 381,304 bytes in 12 blocks
> ==1415992==         suppressed: 0 bytes in 0 blocks
> ==1415992== Reachable blocks (those to which a pointer was found) are not shown.
> ==1415992== To see them, rerun with: --leak-check=full --show-leak-kinds=all
>
> Rerun today with --show-leak-kinds=all (probably not exactly the same GUI actions):
>
> ==7409== LEAK SUMMARY:
> ==7409==    definitely lost: 10,144 bytes in 96 blocks
> ==7409==    indirectly lost: 17,853,762 bytes in 76,878 blocks
> ==7409==      possibly lost: 387,503,190 bytes in 39,004 blocks
> ==7409==    still reachable: 1,366,375 bytes in 4,637 blocks
> ==7409==                       of which reachable via heuristic:
> ==7409==                         newarray           : 376,536 bytes in 10 blocks
> ==7409==         suppressed: 0 bytes in 0 blocks
>
>
> Full logs here:
> J’ai lié 2 fichiers à ce message :
>
> digiKam-9.0.0.valgrind.log
> Taille : 797 Ko
>
> Date d’expiration : 14/08/2026
> NextCloud
> Lien : https://nextcloud.cgiraud.fr/index.php/s/CPQKTzGGPwkHpmy/download
>
> digiKam-9.0.0.valgrind2.log
> Taille : 5.6 Mo
>
> Date d’expiration : 14/08/2026
> Service Filelink : NextCloud
> Lien : https://nextcloud.cgiraud.fr/index.php/s/ap2AqoKHatCKGpG/download
>
> I tried to run digikam 9.1.0 but running appimage with valgrind seems not working.
>
> Best regards,
> Cyril
>
>
>
>
> Le 12/07/2026 à 22:57, Gilles Caulier a écrit :
>
> Hi
> did you observe a potential memory leak? In which context?
>
> You can share the trace in this room using a cloud storage link.
>
> Best regards
>
> Gilles Caulier
>
> Le dim. 12 juil. 2026 à 22:51, Cyril Giraud <cgiraud at free.fr> a écrit :
>
> Hi,
>
> https://www.digikam.org/contribute / Checking for Memory Leaks asks to
> send valgrind output to developers.
>
> Could someone give me an email address or a way to send these outputs?
>
> Thanks !
>
> Cyril
>
>