Re: Sending valgrind logs to...
Gilles Caulier <[email protected]> Mon, 13 Jul 2026 15:16:35 +0200
| Newsgroups | gmane.comp.kde.digikam.user |
|---|---|
| Message-ID | <CAHFG6sEQ3JvvDLO+JmQNSZGdy=FDTmkxMkNFC9e5eiW7v2cS1A@mail.gmail.com> |
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 =C3=A0 13:44, Cyril Giraud <[email protected]> a =C3=A9= crit : > > Hi Gilles, > > Probably yes for digikam 9.0.0 (native for UbuntuStudio 26.04): > =3D=3D1415992=3D=3D LEAK SUMMARY: > =3D=3D1415992=3D=3D definitely lost: 9,208 bytes in 93 blocks > =3D=3D1415992=3D=3D indirectly lost: 17,819,646 bytes in 71,055 blocks > =3D=3D1415992=3D=3D possibly lost: 387,519,486 bytes in 44,750 block= s > =3D=3D1415992=3D=3D still reachable: 1,377,846 bytes in 4,720 blocks > =3D=3D1415992=3D=3D of which reachable via heuristi= c: > =3D=3D1415992=3D=3D newarray : 381,304 = bytes in 12 blocks > =3D=3D1415992=3D=3D suppressed: 0 bytes in 0 blocks > =3D=3D1415992=3D=3D Reachable blocks (those to which a pointer was found)= are not shown. > =3D=3D1415992=3D=3D To see them, rerun with: --leak-check=3Dfull --show-l= eak-kinds=3Dall > > Rerun today with --show-leak-kinds=3Dall (probably not exactly the same G= UI actions): > > =3D=3D7409=3D=3D LEAK SUMMARY: > =3D=3D7409=3D=3D definitely lost: 10,144 bytes in 96 blocks > =3D=3D7409=3D=3D indirectly lost: 17,853,762 bytes in 76,878 blocks > =3D=3D7409=3D=3D possibly lost: 387,503,190 bytes in 39,004 blocks > =3D=3D7409=3D=3D still reachable: 1,366,375 bytes in 4,637 blocks > =3D=3D7409=3D=3D of which reachable via heuristic: > =3D=3D7409=3D=3D newarray : 376,536 byt= es in 10 blocks > =3D=3D7409=3D=3D suppressed: 0 bytes in 0 blocks > > > Full logs here: > J=E2=80=99ai li=C3=A9 2 fichiers =C3=A0 ce message : > > digiKam-9.0.0.valgrind.log > Taille : 797 Ko > > Date d=E2=80=99expiration : 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=E2=80=99expiration : 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 =C3=A0 22:57, Gilles Caulier a =C3=A9crit : > > 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 =C3=A0 22:51, Cyril Giraud <[email protected]> a =C3= =A9crit : > > 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 > >