Konqueror crashes on searches in history file

Bug #6706 reported by Takayama
6
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Fix Released
Medium
Kubuntu Bugs

Bug Description

This is a Dapper-related bug.

Since today, there seems to be a memory leak in konqueror. After entering the first character in the address bar, t freezes for about 3 seconds, then dies.

when started at cli, it tells me:
-------------------
*** glibc detected *** corrupted double-linked list: 0x4033d278 ***
Alarm clock
-------------------

I was able to circumvent the problem by deleting ~/.kde/share/apps/konqueror/*history* , however, it reappeared about 20 minutes later.

Changed in kdebase:
assignee: nobody → kubuntu-team
Revision history for this message
Loic Pefferkorn (loic) wrote :

I cannot reproduce this problem.

Can you please run Konqueror from gdb, and post a backtrace ?

-gdb /usr/bin/konqueror
-type r
-reproduce steps involving crash
-type bt

Post the output here :)

Revision history for this message
ZhengPeng Hou (zhengpeng-hou) wrote :

After fresh install with flight-3 ,this took place in my system .
LANG=en_US
LC_CTYPE=ZH_CN-UTF-8

Revision history for this message
tnoo (answer) wrote :

Exactly this behavior occurs since about two weeks now. It takes about ten lookups in the history bar, then Konqueror (and all of X) freeze. Usually I can kill Konqueror from Terminal 1 (Ctrl+Alt+F1).
Konqueror won't start in the same KDE session anymore.

Revision history for this message
Kenny Duffus (kduffus) wrote :

do you still have this problem with latest updates?

Changed in kdebase:
status: Unconfirmed → Needs Info
Revision history for this message
Martin F. Hohenberg (martin-hohenberg) wrote :

Thankfully, no (with 3.5.2)

Changed in kdebase:
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.