| Summary: | Add a proper GUI warning, when "search and replace" cant handle the amount of files. | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | Matthias <shalokshalom> |
| Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | justin.zobel, kare.sars |
| Priority: | NOR | ||
| Version First Reported In: | Git | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Matthias
2017-06-19 17:06:55 UTC
Thanks for the report. I'm not totally sure what you are after.... What error message are you referring to? Is it about failing to replace a string in a file? It is all about crashing and leaving several hundred documents unsaved, edited and partly replaced. The error message is: (process:2874): GLib-ERROR **: Creating pipes for GWakeup: Too many open files I think it happens maybe only, when i start Kate from fish. Happens in bash too. OK, The problem is that you run out of allowed open file handles. There is a limit for every process of how many files they can have open. https://www.cyberciti.biz/faq/linux-increase-the-maximum-number-of-open-files/ I got: ...$ ulimit -Hn 65536 ...$ ulimit -Sn 1024 You can temporarily increase the number of allowed open files, but adding a proper GUI indication is maybe not so trivial. What should we do about it when we reach that state? Just pop-up an error message or do something? This needs a bit of a discussion... Matthias/Kåre was this ever resolved, can you please test and confirm if the issue still persists, thanks. 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |