Consider filing a bug report against nepomuk but it should definitively
include
- what process (virtuoso_t?) eats
- how much memory ("all" is no information)
- on what configuration (how much memory is nepomuk allowed to acquire
etc.)
ideally, once you spotted the pot. leaking process run it in "valgrind
--tool massif" and attach that log to your bug report.
The question you asked this list is impossible to answer . Consider i'd
ask you "since yesterday i feel cold, why is that?" - you could merely
guess.
Cheers,
Thomas
Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
