Version: (using KDE KDE 3.5.6) Installed from: Debian testing/unstable Packages OS: Linux I had a number (maybe 10) Konqueror windows open, with probably almost all having tabs open. I went to the KDE bug report wizard, into the application selection page, and possibly pressed ctrl-f (for find) or / or something, when Konqueror went into an infinite loop. I have KDE packages from Debian experimental on amd64, with missing packages (at least at the time when I installed them) compiled with apt-get source --build. I'm attaching a backtrace (short and full in the same file) as well as some summary output from oprofile showing in which functions time is spent in the infinite loop. I'll also attach an annotated source showing the lines (all in kdelibs) in which time is spent, in hope all this information provides some insight on how the infinite loop happened.
Created attachment 19621 [details] Backtrace
Created attachment 19622 [details] oprofile output, the functions where time is spent, with call trees
Created attachment 19623 [details] Annotated source files, where the oprofile sampling found the program at sample time (so no exact exec counts, but rough percentages)
I could make this happen again at least once by going to the "Find" list, having chosen "Show most common applications" and left "Keyword Search" blank. Then I did some searches on the page, both with / and ctrl-f. When I pressed Back, konqueror froze in the same way (judging from backtrace).
Can you still reproduce this bug in recent versions? I tried in kde 3.5.9 and couldn't make it "loop" following your instructions in the report and in your last comment.
Nope... I think I haven't ever managed to reproduce this. It just happened once, and I produced the info I could extract from it.
I've tried to open tabs and do searches even using konqueror 4 from trunk and I've got no similar errors.
Since I can't reproduce it in trunk either, WORKSFORME