virtuoso-t process going crazy

Sebastian TrĂ¼g trueg at
Thu Aug 12 08:23:43 BST 2010

Hi Mike,

this is a known issue - sadly I do not know the reason yet. Actually I
am hoping that it is a Virtuoso bug or something that can be "configured
away". One thing that would help is to enable debugging for virtuoso as
I explain below. Then we have data that we can give to the Virtuoso guys
to figure out our problem.

Enabling ODBC debugging:
Create a file ~/.odbc.ini with the following content:

Tracefile = /tmp/iodbc.log
Trace     = 1

Of course you can use whatever log file location you want. Then the next
time Virtuoso goes crazy send me that log (preferably compressed).
Getting the log as quick as possible helps to find the problematic command.


On 08/11/2010 09:53 PM, Michael Jansen wrote:
> Hi
> Since some time it's nearly impossible to use kde without experiencing
> on of virtuoso sissy fits (as i call them) for me.
> For no apparent reason some actions triggers an previously easy system
> with cpu load aroung 1-3% to go to 400% (4core hyperthread here) for as
> long as it wants. All processes are quit (nothing above 2 percent) and
> virtuoso goes all crazy. The longest i had it was for about an hour
> before i got fed up and killed it.
> The trigger can be pretty different. At this moment i have 400% CPU load
> for about half and hour. It was triggered apparently by me starting
> akregator. The system was quit before.
> It sometimes goes on a run when starting firefox but those seem to be short.
> Those trigger are only guesses. So my question is:
> 1. Has someone an idea what happens?
> 2. Has someone an idea how to stop it?
> 3. Has someone an idea how to find out what the reason? Some virtuoso
> debug instructions.
> All trunk here.
> Mike

More information about the kde-core-devel mailing list