virtuoso-t crashes with SIGSEGV often, and almost always after wakeup

[kolen]

When I use KDE envoronment, virtuoso-t crashes quite often, about once per day, sometimes more often. And it crashes almost every time after wakeup, not immediately after wakeup, but after about 1 minute.

Also: bug 981159 (not yet sure if it is the same)

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: virtuoso-opensource-6.1-bin 6.1.6+repack-0ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
CrashCounter: 1
Date: Tue Nov 26 11:04:49 2013
ExecutablePath: /usr/bin/virtuoso-t
ExecutableTimestamp: 1380028829
InstallationDate: Installed on 2013-10-23 (33 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
ProcCmdline: /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_FB1903.ini +wait
ProcCwd: /home/kolen/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend
SegvAnalysis:
 Segfault happened at: 0x939d75: movq $0xffffffffffffffff,(%rax)
 PC (0x00939d75) ok
 source "$0xffffffffffffffff" ok
 destination "(%rax)" (0xffffffffffffffff) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: virtuoso-opensource
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: virtuoso-t crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Harald Sitter (apachelogger)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the Virtuoso program itself, and not with our packages. While we appreciate your issue, it would be better if it was tracked at http://sourceforge.net/p/virtuoso/bugs/, so that the Virtuoso developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!