https://bugs.kde.org/show_bug.cgi?id=513705

            Bug ID: 513705
           Summary: Info Widget -> File View -> Tree Mode: Hang on ticking
                    a folder with many subdirectories and files inside
    Classification: Applications
           Product: ktorrent
      Version First unspecified
       Reported In:
          Platform: EndeavourOS
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

SUMMARY
In the "File" tab, with the tree view selected, on ticking the checkbox on a
folder with many subfolders and files, KTorrent gets hanged. It also stops
Download and Upload processes.
The "tick" operation causes a longer hang (> 100x).

STEPS TO REPRODUCE
1. Load a torrent with a gigantous directory tree (the total file size should
not matter)
2. Open the Files widget and choose the tree view mode
3. tick/untick the checkbox for the root folder

OBSERVED RESULT
KTorrent GUI becomes non-responsive, also stopping the downloads.

EXPECTED RESULT
- The downloads do not get affected.
- Even better if only the files widget (or maybe the whole infowidgetplugin)
becomes non-responsive, but the rest of KTorrent keeps working.

SOFTWARE/OS VERSIONS
KTorrent: master
Operating System: EndeavourOS 
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.18.1-arch1-2 (64-bit)
Graphics Platform: Wayland


ADDITIONAL INFORMATION
My test torrent file contained:
- 1 root directory
- 861 subdirectories
- some of them having ~100 2nd level subdirectories
- a total of 5041 files in subdirectories with the largest being 327MB
- Total size ~89 GB
With the given torrent downloading at the end of the Queue Manager's list and
other torrents also DL/UL-ing well, the hang time with the "untick" action was
~5 seconds, which the "tick" action hanged the DL/UL for ~600 seconds

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to