Bug 221369 - KGet crashed when download list right-clicked [QHashData::nextNode, operator++, Nepomuk::ResourceManagerPrivate::allResourceDataOfType]
Summary: KGet crashed when download list right-clicked [QHashData::nextNode, operator+...
Status: RESOLVED FIXED
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: HI crash
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-05 12:14 UTC by gombang
Modified: 2010-01-14 21:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gombang 2010-01-05 12:14:30 UTC
Application: kget (2.3.85)
KDE Platform Version: 4.3.85 (KDE 4.3.85 (KDE 4.4 Beta2))
Qt Version: 4.6.0
Operating System: Linux 2.6.31.9-174.fc12.i686.PAE i686
Distribution: "Fedora release 12 (Constantine)"

-- Information about the crash:
When I open KGet window, and right-click the download list, KGet crashes.

The crash can be reproduced everytime.

 -- Backtrace:
Application: KGet (kget), signal: Segmentation fault
[Current thread is 1 (Thread 0xb773a7a0 (LWP 2817))]

Thread 2 (Thread 0xb5e05b70 (LWP 2821)):
#0  0x00ae2424 in __kernel_vsyscall ()
#1  0x00443f72 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_timedwait.S:179
#2  0x05f58e70 in wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:85
#3  QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159
#4  0x05f4d76b in QThreadPoolThread::run (this=<value optimized out>) at concurrent/qthreadpool.cpp:140
#5  0x05f57f4f in QThreadPrivate::start (arg=<value optimized out>) at thread/qthread_unix.cpp:244
#6  0x0043fab5 in start_thread (arg=<value optimized out>) at pthread_create.c:297
#7  0x0039683e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb773a7a0 (LWP 2817)):
[KCrash Handler]
#6  QHashData::nextNode (node=0x9e1f4e0) at tools/qhash.cpp:301
#7  0x070da3c8 in operator++ (this=<value optimized out>) at /usr/include/QtCore/qhash.h:350
#8  Nepomuk::ResourceManagerPrivate::allResourceDataOfType (this=<value optimized out>) at /usr/src/debug/kdelibs-4.3.85/nepomuk/core/resourcemanager.cpp:127
#9  0x070da6aa in Nepomuk::ResourceManager::allResourcesOfType (this=<value optimized out>, type=<value optimized out>) at /usr/src/debug/kdelibs-4.3.85/nepomuk/core/resourcemanager.cpp:337
#10 0x070f8be7 in Nepomuk::Tag::allTags () at /usr/src/debug/kdelibs-4.3.85/nepomuk/core/tag.cpp:130
#11 0x070e954e in Nepomuk::TagCloud::updateTags (this=<value optimized out>) at /usr/src/debug/kdelibs-4.3.85/nepomuk/core/ui/kmetadatatagcloud.cpp:69
#12 0x070e9988 in Nepomuk::TagCloud::TagCloud (this=<value optimized out>, parent=<value optimized out>) at /usr/src/debug/kdelibs-4.3.85/nepomuk/core/ui/kmetadatatagcloud.cpp:46
#13 0x080ee9c7 in _start ()

Reported using DrKonqi
Comment 1 Lukas Appelhans 2010-01-05 12:29:14 UTC
This looks quite like bug 219859. Agreed?

Lukas
Comment 2 gombang 2010-01-05 12:50:41 UTC
On Tue, Jan 5, 2010 at 6:29 PM, Lukas Appelhans <l.appelhans@gmx.de> wrote:
> https://bugs.kde.org/show_bug.cgi?id=221369
>
>
> Lukas Appelhans <l.appelhans@gmx.de> changed:
>
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>           Priority|NOR                         |HI
>                 CC|                            |trueg@k3b.org
>
>
>
>
> --- Comment #1 from Lukas Appelhans <l appelhans gmx de>  2010-01-05 12:29:14 ---
> This looks quite like bug 219859. Agreed?
>
> Lukas
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>

Yes, I think so. Not fixed here yet though :(
Comment 3 Lukas Appelhans 2010-01-05 19:55:07 UTC
Sure it should be fixed in trunk if it's related... I hope Sebastian can give us more insight on the issue...

Lukas
Comment 4 Lukas Appelhans 2010-01-14 21:57:29 UTC
Hey!
Sebastian said this is fixed in trunk... thanks for reporting! :)

Lukas