*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY I stumbled upon this one, cackled when I saw it: Making a file huge enough with `yes` command in bash, then compressing it with tar, opening it with kate. I have 32 gigabyes of ram. I don't know what tmpfs allocates by default. STEPS TO REPRODUCE 1. cd /tmpfs 2. yes meow > cat.md 3. # Runs out of space 4. tar czf ~/cat.tar cat.md 5. Go to Dolphin File manager, right click, open with kate. 6. See as the memory surpasses 15 GB in the tar, and instead fills up all the memory, and if the system does not have pages, it hangs. Maybe it "thrashes" but eh. OBSERVED RESULT Saw it hang EXPECTED RESULT Wanted to see some tar binary magic from the output... Maybe I should use the 'cat' command instead... SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.1.103-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-9400F CPU @ 2.90GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 ADDITIONAL INFORMATION Overall, this is a special kinda test, I guess It might be useful as a use case. I'm deleting this account after I make this bug report, or maybe keeping the email for now.
xkill does not stop it, instead use kill 9, after seeing the process with top.
Kate would normally ask on open a very large file, did it ask or did you in the past say to that question 'don't ask again'? In any case, that is just an OOM, expected for that file size and with the tmpfs perhaps not just Kate itself that eats the memory.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
Hi, I'm sorry I didn't get back to you sooner. I loaded up a new installation of Manjaro "manjaro-kde-24.0.6-240812-linux69". Version 24.05.2 of kate. I updated it with pamac and did not change the kernel. The issue does not occur when the file is loaded from a usb stick. Instead, it says that the file is wrapped around, and it is not fully loaded: "The file /run/media/a/Ventoy/cat.tar was opened and contained lines longer than the configured Line Length Limit (10,000 characters). The longest of those lines was 98,479 characters long. Those lines were wrapped and the document is set to read-only mode, as saving will modify its content." Raising the limit does not present any issues. I think on my system, I need to do some spring cleaning, and re-install Manjaro. I find that if I re-install manjaro after a long time, it removes weird issues: high dpi problems from plugging in too many BIG monitors, and this weird OOM issue with kate probably can be fixed if I maintain it by re-installing. I did test this differently. I loaded this file on a 116.06 GIB usb stick, not on my main system. Anyways, thank you for entertaining this report, felt bad for leaving it open. I'll treat it as a weird quirk of my system. If what I now think has something to do with configurations and new kernels, which is highly unlikely, but I'll just make a note here for the mail archives. For now, I'll close the issue. ID-1: /dev/sda vendor: SanDisk model: Cruzer Glide size: 14.59 GiB type: USB ID-2: /dev/sdb model: General USB Flash Disk size: 116.06 GiB type: USB