Bug 221324 - Nepomuk tools take 100% CPU, then crash on input or click [Soprano::FilterModel::addStatement, Soprano::Model::addStatements, Soprano::Util::AddStatementCommand::execute]
Summary: Nepomuk tools take 100% CPU, then crash on input or click [Soprano::FilterMod...
Status: RESOLVED FIXED
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
: 210833 211153 211383 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-01-05 03:48 UTC by Javier Conti
Modified: 2010-01-28 22:40 UTC (History)
5 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 Javier Conti 2010-01-05 03:48:31 UTC
Application: nepomuksimpleannotator (0.1)
KDE Platform Version: 4.3.85 (KDE 4.3.85 (KDE 4.4 Beta2)) "release 203"
Qt Version: 4.6.0
Operating System: Linux 2.6.31.8-0.1-default x86_64
Distribution: "openSUSE 11.2 (x86_64)"

-- Information about the crash:
Everytime I run the following command:

  nepomuksimpleannotator file:///somefile.pdf

The application window pops up, eating 100% of one CPU. Then, as I click or try to input data, it crashes.

Just for info, don't know if it's related, using the nepomuk's resourceeditor command has a very similar behaviour

 -- Backtrace:
Application: Nepomuk Simple PIMO Annotation Shell (nepomuksimpleannotator), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fc76529e7f0 (LWP 16017))]

Thread 3 (Thread 0x7fc754695910 (LWP 16022)):
[KCrash Handler]
#5  0x00007fc7625201e8 in Soprano::FilterModel::addStatement(Soprano::Statement const&) () from /usr/lib64/libsoprano.so.4
#6  0x00007fc7625055c3 in Soprano::Model::addStatements(QList<Soprano::Statement> const&) () from /usr/lib64/libsoprano.so.4
#7  0x00007fc762577e9c in Soprano::Util::AddStatementCommand::execute() () from /usr/lib64/libsoprano.so.4
#8  0x00007fc7630a9989 in QThreadPoolThread::run (this=0x9f4200) at concurrent/qthreadpool.cpp:106
#9  0x00007fc7630b36b5 in QThreadPrivate::start (arg=0x9f4200) at thread/qthread_unix.cpp:244
#10 0x00007fc762e2465d in start_thread () from /lib64/libpthread.so.0
#11 0x00007fc76288614d in clone () from /lib64/libc.so.6
#12 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fc750a0e910 (LWP 16024)):
#0  0x00007fc762e292cd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fc7630b45d2 in wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:85
#2  QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159
#3  0x00007fc7630a9a19 in QThreadPoolThread::run (this=0x16a22e0) at concurrent/qthreadpool.cpp:140
#4  0x00007fc7630b36b5 in QThreadPrivate::start (arg=0x16a22e0) at thread/qthread_unix.cpp:244
#5  0x00007fc762e2465d in start_thread () from /lib64/libpthread.so.0
#6  0x00007fc76288614d in clone () from /lib64/libc.so.6
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fc76529e7f0 (LWP 16017)):
#0  0x00007fc76287d033 in poll () from /lib64/libc.so.6
#1  0x00007fc75caa091a in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007fc75caa0e57 in ?? () from /usr/lib64/libxcb.so.1
#3  0x00007fc75caa1115 in xcb_writev () from /usr/lib64/libxcb.so.1
#4  0x00007fc75f7d103a in _XSend () from /usr/lib64/libX11.so.6
#5  0x00007fc75f7d1561 in _XEventsQueued () from /usr/lib64/libX11.so.6
#6  0x00007fc75f7ba24b in XEventsQueued () from /usr/lib64/libX11.so.6
#7  0x00007fc7641e1ccc in ?? () from /usr/lib64/libQtGui.so.4
#8  0x00007fc7618a1dde in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#9  0x00007fc7618a57a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#10 0x00007fc7618a58d0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#11 0x00007fc7631cfb13 in QEventDispatcherGlib::processEvents (this=0x619410, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#12 0x00007fc7641e194e in ?? () from /usr/lib64/libQtGui.so.4
#13 0x00007fc7631a4e52 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#14 0x00007fc7631a522c in QEventLoop::exec (this=0x7fff37e9ca60, flags=) at kernel/qeventloop.cpp:201
#15 0x00007fc7631a8f7b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#16 0x000000000040bb0c in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/nepomuk/annotation/simpleannotator/resourceannotater.cpp:65

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-05 11:52:20 UTC
From bug 211383 (resourceeditor):
---
What I was doing when the application crashed:
Using virtual folder "nepomuktree" under dolphin, to tag a link associated to a
task (task created by Tasktop), the application crashes when entering the tag.

From bug 211153 (nepomuksimpleannotator):
---
What I was doing when the application crashed:
WIth Dolphin, I select a text file, right click on the file, select "action ->
launch
semantic analysis", nepomuk's windows opens and after few seconds, the crash
occurs.

Bug 210833 is about nepomukshell.

A bit more complete backtrace:
---
Thread 3 (Thread 0xb32f6b70 (LWP 32289)):
[KCrash Handler]
#6  0x09935740 in ?? ()
#7  0xb627f809 in Soprano::FilterModel::addStatement (this=0x9a10e10,
statement=@0x9f52d88) at
/usr/src/debug/soprano-2.3.1/soprano/filtermodel.cpp:93
#8  0xb6264437 in Soprano::Model::addStatements (this=0x9a10e10,
statements=@0xb32f62c8) at /usr/src/debug/soprano-2.3.1/soprano/model.cpp:141
#9  0xb62d7a80 in Soprano::Util::AddStatementCommand::execute (this=0x9fa5af0)
at /usr/src/debug/soprano-2.3.1/soprano/util/asynccommand.cpp:101
#10 0xb62d945f in Soprano::Util::Command::run (this=0x9fa5af0) at
/usr/src/debug/soprano-2.3.1/soprano/util/asynccommand.h:60
#11 0xb65a3353 in QThreadPoolThread::run (this=0x99849b8) at
concurrent/qthreadpool.cpp:106
#12 0xb65acec3 in QThreadPrivate::start (arg=0x99849b8) at
thread/qthread_unix.cpp:188
#13 0xb615c885 in start_thread () from /lib/i686/libpthread.so.0
#14 0xb63e857e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Comment 2 Dario Andres 2010-01-05 11:52:41 UTC
*** Bug 210833 has been marked as a duplicate of this bug. ***
Comment 3 Dario Andres 2010-01-05 11:52:45 UTC
*** Bug 211383 has been marked as a duplicate of this bug. ***
Comment 4 Dario Andres 2010-01-05 11:53:11 UTC
*** Bug 211153 has been marked as a duplicate of this bug. ***
Comment 5 Sebastian Trueg 2010-01-18 12:18:48 UTC
I cannot reproduce it with KDE 4.4rc1.
Comment 6 Sebastian Trueg 2010-01-27 13:20:54 UTC
Please verify that this is fixed in KDE 4.4rc2
Comment 7 Javier Conti 2010-01-28 21:04:28 UTC
On 27 January 2010 13:21, Sebastian Trueg <trueg@k3b.org> wrote:
> https://bugs.kde.org/show_bug.cgi?id=221324
>
>
> Sebastian Trueg <trueg@k3b.org> changed:
>
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Status|UNCONFIRMED                 |NEEDSINFO
>         Resolution|                            |WAITINGFORINFO
>
>
>
>
> --- Comment #6 from Sebastian Trueg <trueg k3b org>  2010-01-27 13:20:54 ---
> Please verify that this is fixed in KDE 4.4rc2

I confirm the crash does not to happen anymore to me in the following version:

$ resourceeditor --version
Qt: 4.6.1
KDE Development Platform: 4.3.95 (KDE 4.3.95 (KDE 4.4 RC2)) "release 214"
ResourceEditor: 0.1

>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>