Bug 294184 - Crash when accessing videos from slow media [QDBusConnectionPrivate::~QDBusConnectionPrivate ]
Summary: Crash when accessing videos from slow media [QDBusConnectionPrivate::~QDBusCo...
Status: RESOLVED WORKSFORME
Alias: None
Product: gwenview
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.7
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: Gwenview Bugs
URL:
Keywords:
: 296527 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-02-15 20:39 UTC by Alex Dănilă
Modified: 2018-11-30 12:51 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Dănilă 2012-02-15 20:39:29 UTC
Application: gwenview (2.7.4)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.8.0
Operating System: Linux 3.2.0-1-amd64 x86_64
Distribution: Debian GNU/Linux 5.0.9 (lenny)

-- Information about the crash:
- What I was doing when the application crashed:
Clicked on a video from a slow SD card, expecting it to be opened in Gwenview. Gwenview did open, but it seems it remained hanged after closing. The processor was 100% percent used by some mplayer processes, so I killed them. After killing those mplayer processes, the KDE crash handler for Gwenview appeared.

- Unusual behavior I noticed:
Two mplayer processes where using the processor to 100%.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3578e2e760 (LWP 5338))]

Thread 3 (Thread 0x7f3563e16700 (LWP 5349)):
#0  __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97
#1  0x00007f357577c3f8 in _L_lock_9627 () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007f357577a7e1 in *__GI___libc_free (mem=0x7f3575a82e60) at malloc.c:3736
#3  0x00007f3577c8d4a5 in socketNotifierSourceCheck (source=0x1105280) at kernel/qeventdispatcher_glib.cpp:92
#4  0x00007f357205ed7e in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f357205f5f2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f357205fa99 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007f3577c8dd8f in QEventDispatcherGlib::processEvents (this=0x1100a50, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#8  0x00007f3577c5d5f2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#9  0x00007f3577c5d847 in QEventLoop::exec (this=0x7f3563e15df0, flags=...) at kernel/qeventloop.cpp:204
#10 0x00007f3577b5d307 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#11 0x00007f3577c3d3af in QInotifyFileSystemWatcherEngine::run (this=0x10ff7f0) at io/qfilesystemwatcher_inotify.cpp:248
#12 0x00007f3577b6032b in QThreadPrivate::start (arg=0x10ff7f0) at thread/qthread_unix.cpp:298
#13 0x00007f3572926b50 in start_thread (arg=<optimized out>) at pthread_create.c:304
#14 0x00007f35757d890d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#15 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f3553a42700 (LWP 5704)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:39
#1  0x00007f3577b5edfb in _q_futex (val2=0, addr2=0x0, timeout=0x0, val=2, op=0, addr=0x1612cf0) at thread/qmutex_unix.cpp:99
#2  QMutexPrivate::wait (this=0x1612cf0, timeout=<optimized out>) at thread/qmutex_unix.cpp:113
#3  0x00007f3577b5abcd in QMutex::lockInternal (this=<optimized out>) at thread/qmutex.cpp:450
#4  0x00007f3578762578 in ?? () from /usr/lib/libgwenviewlib.so.4
#5  0x00007f3577b6032b in QThreadPrivate::start (arg=0x16086a0) at thread/qthread_unix.cpp:298
#6  0x00007f3572926b50 in start_thread (arg=<optimized out>) at pthread_create.c:304
#7  0x00007f35757d890d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#8  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f3578e2e760 (LWP 5338)):
[KCrash Handler]
#6  malloc_consolidate (av=0x7f3575a82e60) at malloc.c:5153
#7  0x00007f35757773e8 in _int_free (av=0x7f3575a82e60, p=0x1e3c3d0) at malloc.c:5034
#8  0x00007f357577a7ec in *__GI___libc_free (mem=<optimized out>) at malloc.c:3738
#9  0x00007f3572fcf40e in ~QDBusMetaObject (this=<optimized out>, __in_chrg=<optimized out>) at qdbusmetaobject_p.h:75
#10 qDeleteAll<QHash<QString, QDBusMetaObject*>::const_iterator> (end=..., begin=...) at ../../include/QtCore/../../src/corelib/tools/qalgorithms.h:322
#11 qDeleteAll<QHash<QString, QDBusMetaObject*> > (c=...) at ../../include/QtCore/../../src/corelib/tools/qalgorithms.h:330
#12 QDBusConnectionPrivate::~QDBusConnectionPrivate (this=0x11003d0, __in_chrg=<optimized out>) at qdbusintegrator.cpp:1012
#13 0x00007f3572fcf6b9 in QDBusConnectionPrivate::~QDBusConnectionPrivate (this=0x11003d0, __in_chrg=<optimized out>) at qdbusintegrator.cpp:1021
#14 0x00007f3572fc4913 in ~QDBusDefaultConnection (this=0x10ffe40, __in_chrg=<optimized out>) at qdbusconnection.cpp:1120
#15 QGlobalStaticDeleter<QDBusDefaultConnection>::~QGlobalStaticDeleter (this=0x7f3573228c98, __in_chrg=<optimized out>) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1923
#16 0x00007f3575736df2 in __run_exit_handlers (status=0, listp=0x7f3575a814c8, run_list_atexit=true) at exit.c:78
#17 0x00007f3575736e45 in *__GI_exit (status=1973956192) at exit.c:100
#18 0x00007f357571eeb4 in __libc_start_main (main=<optimized out>, argc=<optimized out>, ubp_av=<optimized out>, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff287153a8) at libc-start.c:260
#19 0x00000000004262d1 in _start ()

Reported using DrKonqi
Comment 1 Jekyll Wu 2012-05-29 03:17:42 UTC
*** Bug 296527 has been marked as a duplicate of this bug. ***
Comment 2 Andrew Crouthamel 2018-10-29 22:40:25 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-11-13 14:36:49 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2018-11-29 09:37:59 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 5 Alex Dănilă 2018-11-30 12:51:14 UTC
(In reply to Andrew Crouthamel from comment #2)
> Dear Bug Submitter,
> 
> This bug has been stagnant for a long time. Could you help us out and
> re-test if the bug is valid in the latest version? I am setting the status
> to NEEDSINFO pending your response, please change the Status back to
> REPORTED when you respond.
> 
> Thank you for helping us make KDE software even better for everyone!


Hi, unfortunately I can't find any slow SD (or any other storage), did it work well for you? 

Otherwise, I'm not sure what is the point of these changes (->NEEDSINFO->WORKSFORME). Is it just to decrease the number of bugs reported by this tracker?