|
Bugzilla – Full Text Bug Listing |
| Summary: | beagle creates lots of tmp files in /tmp | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Andreas Jaeger <aj> |
| Component: | Mono | Assignee: | Gary Ekker <gekker> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | ||
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | a patch which fixes this problem | ||
|
Description
Andreas Jaeger
2005-08-28 10:47:48 UTC
It's normal to have a handful of these while the beagle daemon is running, and they're cleaned up when finished. Do these stick around after you shut down the daemon? If so, can you attach your ~/.beagle/Log/current-IndexHelper for the run in which they're created? Ok, started beagled again and after a couple of minutes I have 208 tmp* files in /tmp/ created by beagled. Andreas: The logfile you attached suggests that the problem is in the Akregator backend, but I haven't been able to reproduce it. Could you look at some of the left-over tmp files and see if you can tell where the fulltexts they contain are coming from? If they contain data from looks like it comes from RSS feeds, that would at least help us narrow things down. A partial fix for this is in RC1. We still leak tmp files in some cases, but at a slower rate. If I can't track down the logical error that is causing this (propably an exception or error condition we are not handling correctly) fairly quickly on Tuesday, I'll work around it for RC2 by periodically cleaning up /tmp. OK, I tracked this down to a logic error --- so there is no need for a work around. This is now fixed in beagle CVS. do you have a patch for 10.0? Created attachment 49141 [details]
a patch which fixes this problem
submitted for RC2 |