qdbus org.kde.nepomuk.services.nepomukqueryservice /nepomukqueryservice/query142 queryString select distinct ?r ?reqProp1 (bif:concat(bif:search_excerpt(bif:vector('sven'), ?v6))) as ?_n_f_t_m_ex_ where { { ?r <http://akonadi-project.org/ontologies/aneo#akonadiItemId> ?reqProp1 . ?r <http://www.semanticdesktop.org/ontologies/2007/03/22/nmo#bcc> ?v2 . ?v2 <http://www.semanticdesktop.org/ontologies/2007/03/22/nmo#cc> ?v3 . ?v3 <http://www.semanticdesktop.org/ontologies/2007/03/22/nmo#to> ?v4 . ?v4 <http://www.semanticdesktop.org/ontologies/2007/03/22/nco#hasEmailAddress> ?v5 . ?v5 <http://www.semanticdesktop.org/ontologies/2007/03/22/nco#emailAddress> ?v6 . FILTER(bif:contains(?v6, "'sven'")) . ?r a <http://www.semanticdesktop.org/ontologies/2007/03/22/nmo#Email> . } . ?r <http://www.semanticdesktop.org/ontologies/2007/08/15/nao#userVisible> ?v1 . FILTER(?v1>0) . } Reproducible: Always Steps to Reproduce: 1. resume from suspend (s2ram) 2. find virtuoso-t hogging the cpu Actual Results: high cpu usage Expected Results: low cpu usage kmail hangs and has to be killed. This does not decrease virtuoso's cpu usage though. atoping akonadi, i.e. no akonadi processes left does not solve the issue either. rpm -qa | grep virtuoso soprano-backend-virtuoso-2.7.5-120.1.i586 virtuoso-drivers-6.1.5-59.1.i586 virtuoso-server-6.1.5-59.1.i586
I have this problem also in KDE 4.9
Can confirm this in KDE 4.9.2 - full load on one CPU-Core and some 500MB RAM consumption rpm -qa | grep virtuoso virtuoso-drivers-6.1.6-61.1.x86_64 soprano-backend-virtuoso-2.8.0-120.1.x86_64 virtuoso-server-6.1.6-61.1.x86_64
Confirming the same behaviour of virtuoso-t (high CPU usage) on Kubuntu 12.10 running KDE 4.9.2: plahapla@kplaha:~$ dpkg -l *virtuoso* ii virtuoso-minimal 6.1.6+repack-0ubuntu1 all high-performance database - core dependency package ii virtuoso-opensource-6.1-bin 6.1.6+repack-0ubuntu1 amd64 high-performance database - binaries ii virtuoso-opensource-6.1-common 6.1.6+repack-0ubuntu1 amd64 high-performance database - common files
This particular query has been fixed in 4.10