Summary: | crash after vm.max_map_count limit reached on gigabit connection | ||
---|---|---|---|
Product: | [Applications] ktorrent | Reporter: | avi9526 <dromaretsky> |
Component: | general | Assignee: | Joris Guisson <joris.guisson> |
Status: | REPORTED --- | ||
Severity: | crash | CC: | justin.zobel |
Priority: | NOR | ||
Version: | 22.08.2 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
avi9526
2018-07-03 21:45:14 UTC
Link to Arch forum topic https://bbs.archlinux.org/viewtopic.php?id=238475 So it seems this was related to virtual memory? Can this now be closed? KTorrent carshes with default vm.max_map_count this is not ok When vm.max_map_count increased KTorrent not crashing, but it has random freezes - speed goes up to 100MB/s, then freeze for few seconds, then unfreeze and speeds drop, repeat. Also this freeze cause system to lag - video player lag on HD videos Forgive me if I'm wrong but the OS sets this value right? (In reply to Justin Zobel from comment #4) > Forgive me if I'm wrong but the OS sets this value right? https://www.kernel.org/doc/Documentation/sysctl/vm.txt The default value is 65536. Thanks for the information, setting back to reported for investigation. Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! ktorrent 22.08.2 still crashing when vm.max_map_count limit reached |