After searching for a name within the content of all files in my home folder - kfind takes a very long time (many files I guess!) and then crashes in the end with this message: [code] kfind(13576) KQuery::processQuery: ignoring, not a text file: KUrl("file:///home/piedro/VMs/Isoz/linuxmint-17.3-cinnamon-64bit.iso") Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there. terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc KCrash: Application 'kfind' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/piedro/.kde4/socket-arch/kdeinit4__0 [/code] Now first of all - I do not know why kfind searches within *.iso files and Virtualbox images... this should be avoided somehow (maybe by preference profiles?). Why it crashes - I do not know - but looks like a big bug to me. Essentially this crashes every search for the content of files. Reproducible: Always Steps to Reproduce: 1. search for a name you know you have in some files in your home folder 2. let it kfind run a long time 3. wait for it to crash Actual Results: crashes Expected Results: shouldn't crash If kfind is to be used within dolphin searches soon - it should not refer to ".kde4" directories, should it?
Oops, my bad! It's nothing to do with the "*.iso" file - as the message clearly says: [quote]...ignoring, not a text file:... [/quote] Sorry for that but the crashing continues: [code]Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there. terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc KCrash: Application 'kfind' crashing... [/code] p.
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 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!
Sry, I do not use KDE anymore. Thx for the notice... p.
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!