Bug 179682 - crash when opening a new tab using
Summary: crash when opening a new tab using
Status: RESOLVED FIXED
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kdeui (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-05 03:59 UTC by Vitali Lovich
Modified: 2009-07-22 19:57 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vitali Lovich 2009-01-05 03:59:59 UTC
Version:           2.1 (using KDE 4.1.3)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Ubuntu Packages

Opening a tab for the konsole session segfaults & terminates all tabs & windows for that session.  Opening a new window instead doesn't do this (although opening a new tab in the new window kills both windows).

Here's a stack trace.  Note that the kpixmapcache.cpp:643 line repeats indefinitely(with the all the same values).  I did a "where -1" to try and see what originated this, but my computer was chugging away full-speed for like 5 minutes before I gave up.

Strangely, this only happens with my laptop (Ubuntu) & not on my desktop (Kubuntu).  I've tried blowing away my .kde profile, but that didn't help.  This is reproducible every time which is really annoying cause I got used to opening tabs.
 
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(gdb) r
Starting program: /usr/bin/konsole --nofork
[Thread debugging using libthread_db enabled]
[New Thread 0x7f22403406f0 (LWP 9864)]
[New Thread 0x41bb4950 (LWP 9867)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f22403406f0 (LWP 9864)]
0x00007f223fb6f4a8 in _int_malloc () from /lib/libc.so.6
(gdb) thread apply all backtrace
Thread 2 (Thread 0x41bb4950 (LWP 9867)):
#0  0x00007f223fbd2482 in select () from /lib/libc.so.6
#1  0x00007f223e6cf006 in ?? () from /usr/lib/libQtCore.so.4
#2  0x00007f223e606362 in ?? () from /usr/lib/libQtCore.so.4
#3  0x00007f223a1273ea in start_thread () from /lib/libpthread.so.0
#4  0x00007f223fbd9c6d in clone () from /lib/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f22403406f0 (LWP 9864)):
#0  0x00007f223fb6f4a8 in _int_malloc () from /lib/libc.so.6
#1  0x00007f223fb70a24 in _int_realloc () from /lib/libc.so.6
#2  0x00007f223fb71abe in realloc () from /lib/libc.so.6
#3  0x00007f223e62860b in QListData::realloc () from /usr/lib/libQtCore.so.4
#4  0x00007f223e62882b in QListData::append () from /usr/lib/libQtCore.so.4
#5  0x00007f223e68b60f in ?? () from /usr/lib/libQtCore.so.4
#6  0x00007f223e687001 in QIODevice::seek () from /usr/lib/libQtCore.so.4
#7  0x00007f223f022848 in KPixmapCache::Private::binarySearchKey (
    this=0x2452890, stream=@0x7fff4836d020, key=@0x185c000, start=33)
    at /build/buildd/kde4libs-4.1.3/kdeui/icons/kpixmapcache.cpp:628
#8  0x00007f223f02291d in KPixmapCache::Private::binarySearchKey (
    this=0x2452890, stream=@0x7fff4836d020, key=@0x7fff4836d0d0, 
    start=<value optimized out>)
---Type <return> to continue, or q <return> to quit---
    at /build/buildd/kde4libs-4.1.3/kdeui/icons/kpixmapcache.cpp:643
#9  0x00007f223f02291d in KPixmapCache::Private::binarySearchKey (
    this=0x2452890, stream=@0x7fff4836d020, key=@0x7fff4836d0d0, 
    start=<value optimized out>)
    at /build/buildd/kde4libs-4.1.3/kdeui/icons/kpixmapcache.cpp:643
#10 0x00007f223f02291d in KPixmapCache::Private::binarySearchKey (
    this=0x2452890, stream=@0x7fff4836d020, key=@0x7fff4836d0d0, 
    start=<value optimized out>)

Thanks
Comment 1 Christoph Feck 2009-05-25 20:43:34 UTC
Reassigning
Comment 2 vlovich+kdebugs 2009-05-25 20:48:45 UTC
This bug appears to have disappeared in one of the updates since then & presumably has been fixed, although it's annoying that when one Konsole window crashes, they all crash.
Comment 3 Christoph Feck 2009-07-22 19:57:38 UTC
Reporter says it's fixed. The report was for KDE 4.1.3.