SUMMARY I try to extract tens of large zip files with KDE dolphin,and each zip is 1~2 GB after extracted (by selecting them in dolphin right -> click extract and detect subfolder). Ark ends up exhausting the 16 GB memory in my computer during the extraction. OBSERVED RESULT Ark uses up all of my 16 GB memory during extraction of multiple files. EXPECTED RESULT Ark should not use memory larger than one file. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Hey there Jon, I cant reproduce this using ARK 19.04.3. Could you please provide the full information from the original template? This includes SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Have you been able to reproduce this with all archives or is only one giving you issues?
Do you mean you have tens of Ark processes that use all your memory?
After further examination, I cannot reproduce it on another zip files on a similar Arch system. The file I had problems with is zip files with thousands of jpeg files. Since I cannot access that computer in the next few days, I cannot provide further exact information for now. Also, there was only one ark process; something like: ark file1.zip file2.zip file3.zip file4.zip ... (In reply to Kitsuna from comment #1) > Hey there Jon, I cant reproduce this using ARK 19.04.3. Could you please > provide the full information from the original template? This includes > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: > (available in About System) > KDE Plasma Version: > KDE Frameworks Version: > Qt Version: > > Have you been able to reproduce this with all archives or is only one giving > you issues?
(In reply to Kitsuna from comment #1) > Hey there Jon, I cant reproduce this using ARK 19.04.3. Could you please > provide the full information from the original template? This includes > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: > (available in About System) > KDE Plasma Version: > KDE Frameworks Version: > Qt Version: > > Have you been able to reproduce this with all archives or is only one giving > you issues? Hello, this is my environment Operating System: Arch Linux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 Kernel Version: 5.2.0-arch2-1-ARCH OS Type: 64-bit Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 15.5 GiB The files I extracted are: Before extracted => 34.2 GiB, 29 files After extracted => 32.5 GiB, 422535 files, 451 folders htop shows, and this process uses more and more memory during the extraction. /usr/bin/ark --batch --autodestination --autosubfolder a.zip b.zip ... I mount tmpfs to /tmp. While I have wondered that whether ark makes use use of /tmp and thus exhausts my memory, it does not. Maybe it is memory leak of ark under certain conditions? Thanks.
Appendix: It seems that valgrind reports the memory leak. ==18967== Memcheck, a memory error detector ==18967== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==18967== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info ==18967== Command: ark -b -a -e a.zip ==18967== ==18967== ==18967== HEAP SUMMARY: ==18967== in use at exit: 649,087,909 bytes in 198,712 blocks ==18967== total heap usage: 1,445,746 allocs, 1,247,034 frees, 1,087,496,989 bytes allocated ==18967== ==18967== LEAK SUMMARY: ==18967== definitely lost: 1,230,634 bytes in 16,528 blocks ==18967== indirectly lost: 638,863,808 bytes in 114,987 blocks ==18967== possibly lost: 2,308,808 bytes in 132 blocks ==18967== still reachable: 6,684,659 bytes in 67,065 blocks ==18967== suppressed: 0 bytes in 0 block
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Please refer to comment 4-5