[ktorrent] [Bug 485756] ktorrent bad_alloc

2024-07-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=485756 lg3dx...@gmail.com changed: What|Removed |Added CC||lg3dx...@gmail.com -- You are receiving

[ktorrent] [Bug 485756] ktorrent bad_alloc

2024-04-18 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=485756 --- Comment #5 from lg3dx...@gmail.com --- Some really smart guys from IRC #gentoo said it can relate to kernel overcommiting https://www.kernel.org/doc/html/latest/mm/overcommit-accounting.html After # root : sysctl vm.overcommit_memory=1 I cannot

[ktorrent] [Bug 485756] ktorrent bad_alloc

2024-04-18 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=485756 --- Comment #4 from lg3dx...@gmail.com --- I guess it somehow relates to the bug https://bugs.kde.org/show_bug.cgi?id=45 -- You are receiving this mail because: You are watching all bug changes.

[ktorrent] [Bug 485756] ktorrent bad_alloc

2024-04-18 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=485756 --- Comment #3 from lg3dx...@gmail.com --- recompiled with -fsanitize=address -fsanitize=leak -O0 -march=native -ggdb3 . got this at roughlt 60 MiB/s download speed ==9516==ERROR: AddressSanitizer: out of memory: failed to allocate 0x1000 (4096) bytes

[ktorrent] [Bug 485756] ktorrent bad_alloc

2024-04-18 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=485756 --- Comment #2 from lg3dx...@gmail.com --- recompiled with -O0 -march=native -ggdb3 , no lto at roughly 102.65 MiB/s it crashed with bad_alloc [Thread 0x7fffd2ca46c0 (LWP 160020) exited] Warning: Qt has caught an exception thrown from an event

[ktorrent] [Bug 485756] ktorrent bad_alloc

2024-04-18 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=485756 --- Comment #1 from lg3dx...@gmail.com --- recompiled without lto, got another bad_alloc: backtrace: [Thread 0x7fffcddc96c0 (LWP 79595) exited] Warning: Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler