Version: (using KDE KDE 3.1.1) Installed from: Debian testing/unstable Packages OS: Linux I have encountered a problem also described by various other people e.g.on the debian-kde mailing list in May 2003 (http://lists.debian.org/debian-kde/2003/debian-kde-200305/msg00070.html): Suddenly konqueror would eat up all memory (1024MB in 1-3 secs) until I kill it manually or the kernel kills it. This happens with any page, usually with the first page. Sometimes, however, the first page renders, but then clicking on a link will produce the same result. I cannot give you steps on how to reproduce the problem. I know, however, how I solved the problem for me, so I hope this might give you an indication as to where the problem was: I seem to have fixed the problem on my system (for now at least) by deleting three files in ~/.kde/share/apps/konqueror/: ~/.kde/share/apps/konqueror/bookmarks.xml.tbcache ~/.kde/share/apps/konqueror/faviconrc ~/.kde/share/apps/konqueror/konq_history The bookmarks.xml.tbcache file was 0-size in my case (while the bookmarks.xml file is ca. 65k) - something which didn't seem right. I don't know which of those was responsible for the hick-up, but it all works now. Many thanks for such an excellent browser :-) Cheers -Tim
Please try: ulimit -v 80000 ulimit -c unlimited export KDE_DEBUG=yes konqueror <yourpage> and then wait til it crashes gdb konqueror core
(a) This bug is confirmed. Problem was the same for others (see url in initial report), and my solution fixed the problem also for at least one other person (http://lists.debian.org/debian-kde/2003/debian-kde-200305/msg00220.html) (b) Fortunately for me, but unfortunately for purposes of debugging, I cannot reproduce this bug any longer after deleting those three files. sorry. I've tried creating an empty bookmarks.xml.tbcache, but that alone did not trigger the bug, so it must have had to do with the 'faviconrc' and/or konq_history file. Sorry. I will try what you suggest next time I come across something like that. Sorry I didn't think about ulimit before. Many thanks, esp. for the fast reponse. Cheers -Tim
sorry, but then I have to close it as package bug. I only heard users of debian testing having that problem.