Bug 227041 - nepomuk memory climbs to ~2.0 GB then crashes and repeats
Summary: nepomuk memory climbs to ~2.0 GB then crashes and repeats
Status: RESOLVED FIXED
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-15 18:38 UTC by Jesse Milette
Modified: 2010-03-15 14:08 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Milette 2010-02-15 18:38:29 UTC 
Version:            (using KDE 4.4.0)
OS:                Linux
Installed from:    Ubuntu Packages

After enabling the file indexer, the strigi indexer process starts eating memory at absurd rates until it has used around 2 GB of memory (????) then crashes and repeats the process.  It does actually index files as i can search for them and the database is only ~200mb.  I have the memory usage for Strigi set to 50mb, and it is obviously not working.
Comment 1 Sebastian Trueg 2010-02-16 13:00:07 UTC 
You cannot change the memory usage for strigi. You can only change the memory usage for the Virtuoso server.
Which process is actually eating memory? There are several "nepomukservicestub" ones. What I need is the parameters. You can get that via "ps aux"
Comment 2 Jesse Milette 2010-03-05 15:06:47 UTC 
the issue actually stopped, i think it was related to indexing some very large mp4 files i have sitting around.  The process was nepomukservices nepomukstrigiservice.