Bug 169105 - dolphin crashed when loading up a large directory on ntfs partition
Summary: dolphin crashed when loading up a large directory on ntfs partition
Status: RESOLVED DUPLICATE of bug 163171
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-14 09:59 UTC by Piotr Mitas
Modified: 2008-09-14 19:15 UTC (History)
1 user (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 Piotr Mitas 2008-08-14 09:59:04 UTC
Version:           1.1 (using 4.1.00 (KDE 4.1.0), Kubuntu packages)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-20-generic

Dolphin crashed when trying to view a large ntfs directory (windows/system32). 

Here's the backtrace:

Program: Dolphin (dolphin), sygnał SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5eeba80 (LWP 8782)]
[New Thread 0xb4355b90 (LWP 8790)]
[KCrash handler]
#6  0xb75f2c80 in QUrl::host () from /usr/lib/libQtCore.so.4
#7  0xb7d7c121 in searchIdleList (idleSlaves=@0x81e0a44, url=@0x60, 
    protocol=@0xbfd736bc, exact=@0xbfd7375b)
    at /build/buildd/kde4libs-4.1.0/kio/kio/scheduler.cpp:608
#8  0xb7d7c6be in KIO::SchedulerPrivate::findIdleSlave (this=0x81e09f0, 
    job=0x877a190, exact=@0xbfd7375b)
    at /build/buildd/kde4libs-4.1.0/kio/kio/scheduler.cpp:682
#9  0xb7d7ecfa in KIO::SchedulerPrivate::startJobDirect (this=0x81e09f0)
    at /build/buildd/kde4libs-4.1.0/kio/kio/scheduler.cpp:587
#10 0xb7d7edd8 in KIO::SchedulerPrivate::startStep (this=0x81e09f0)
    at /build/buildd/kde4libs-4.1.0/kio/kio/scheduler.cpp:432
#11 0xb7d7ef97 in KIO::Scheduler::qt_metacall (this=0x8191068, 
    _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfd73838)
    at /build/buildd/kde4libs-4.1.0/obj-i486-linux-gnu/kio/scheduler.moc:101
#12 0xb76494f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb7649bc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb7686e07 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#15 0xb765067e in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#16 0xb7644c9a in QObject::event () from /usr/lib/libQtCore.so.4
#17 0xb6bbdc0c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#18 0xb6bc27a9 in QApplication::notify () from /usr/lib/libQtGui.so.4
#19 0xb7ac8f53 in KApplication::notify (this=0xbfd73f8c, receiver=0x81e09f4, 
    event=0xbfd73d18)
    at /build/buildd/kde4libs-4.1.0/kdeui/kernel/kapplication.cpp:311
#20 0xb76346a9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#21 0xb76621a1 in ?? () from /usr/lib/libQtCore.so.4
#22 0xb765fa40 in ?? () from /usr/lib/libQtCore.so.4
#23 0xb628bdd6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb628f193 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb628f74e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb765ff98 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#27 0xb6c511b5 in ?? () from /usr/lib/libQtGui.so.4
#28 0xb763392d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#29 0xb7633abd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#30 0xb7635d3d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#31 0xb6bbd567 in QApplication::exec () from /usr/lib/libQtGui.so.4
#32 0x08080aa9 in ?? ()
#33 0xb6731450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#34 0x08061a71 in _start ()
#0  0xb7ef2410 in __kernel_vsyscall ()
Comment 1 Frank Reininghaus 2008-09-11 18:22:23 UTC
Thanks for the bug report. The backtrace looks like the one of bug 163171, it might be a duplicate of this bug.
Comment 2 Frank Reininghaus 2008-09-14 11:32:58 UTC
It would be helpful if you could provide the following information (none of the duplicate candidates seems to contain this):

- which view mode (icons, details, column) did you use?
- has the preview been turned on?
- does the crash occur very rarely or is it reproducible by going to the problematic directory?

Thanks!
Comment 3 Piotr Mitas 2008-09-14 12:53:03 UTC
- I used the icons view mode
- I *think* the preview was on
- As far as I remember, it occurred a few times in different directories while they where loading up, maybe when they were loading previews, I don't remember... 

As for me, I recently switched back from Kubuntu/KDE4.1 to Gentoo/KDE 3.5 so I'm afraid I won't be of much help here anymore.
Comment 4 Frank Reininghaus 2008-09-14 19:15:01 UTC
Piotr, thanks for the quick reply! Actually, I could get 4.1.1 to crash two times now in folders with many files in Icon View with previews enabled, but it's still not really reproducible for me.

I'm pretty sure it's a duplicate, I'll mark this report accordingly.

*** This bug has been marked as a duplicate of bug 163171 ***