Bug 223225 - kontact crash after sending TERM signal - __poll (fds, nfds, timeout=16286) at ../sysdeps/unix/sysv/linux/poll.c:87
Summary: kontact crash after sending TERM signal - __poll (fds, nfds, timeout=16286) a...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-18 00:48 UTC by PC LX
Modified: 2017-06-24 00:25 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 PC LX 2010-01-18 00:48:55 UTC
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.31.6-desktop-1mnb x86_64
Distribution: "Mandriva Linux 2010.0"

What I was doing when the application crashed:
After closing kontact's window to terminate kontact, kontact's process was left running. After some time, far more than usually needed to terminate, I sent it a TERM signal and the result was this crash.

So the bug is two fold. First the kontact was left "stuck" and did not terminate as it should have. Second, sending it a TERM signal caused this crash.


 -- Backtrace:
Application: Kontact (kontact), signal: Aborted
[KCrash Handler]
#26 0x00007f448bcf07f3 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=16286) at ../sysdeps/unix/sysv/linux/poll.c:87
#27 0x00007f4485931c7c in g_main_context_iterate (context=0x25efb30, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2904
#28 0x00007f4485931fc0 in IA__g_main_context_iteration (context=0x25efb30, may_block=1) at gmain.c:2654
#29 0x00007f448cf94c73 in QEventDispatcherGlib::processEvents (this=0x25b1690, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:406
#30 0x00007f448c4ae64e in QGuiEventDispatcherGlib::processEvents (this=0x6609700, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#31 0x00007f448cf6afe2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#32 0x00007f448cf6b3b4 in QEventLoop::exec (this=0x7fff4aa9db00, flags=) at kernel/qeventloop.cpp:201
#33 0x00007f448cf6d569 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#34 0x0000000000403be7 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.3.2/kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Christoph Feck 2013-09-12 21:38:48 UTC
This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)