Version: 4.0.1 (using KDE 4.4.5) OS: Linux As subject line/below. I'm not entirely sure if bad argument passing to xargs or an external bug is to blame, but a symptom of this is that the "find in files" result window can easily be filled with huge volumes of output making kdevelop respond very poorly (possibly just while the output is being copied to this frame; not sure). Thus it would be a good idea additionally to have a restriction on the amount of content that this frame can take or a warning with an option to abort when too much content is injected (can't give much info on a sensible limit, sorry). Reproducible: Always Steps to Reproduce: Search in all files for any string ending with an LF (0x0A) character (warning: I'd advise picking a directory to search in containing only a few files to avoid the responsiveness issues described above). Actual Results: All lines of all files are found, resulting in a lot of output and poor performance of kdevelop. Expected Results: Some kind of catch to prevent such unresponsive behaviour, and either for the bad (multiline) regular expression to result in an error message rather than incorrect matches or for it to match across lines properly.
I can confirm this with kdevelop 4.7 in a similar scenario: I accidentally forget to put the build directory in the Exclude list of File Files dialog. So the search result includes an .so file which results in garbage unicode letter printed in the results view and kdevelop stops responding. I had to kill it.
screenshot of garbage binary output: http://wstaw.org/m/2014/09/21/plasma-desktopOs2057.png
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
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!
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!