After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 419389 - huge log file (probable svg filter loop)
huge log file (probable svg filter loop)
Status: RESOLVED INCOMPLETE
Product: beagle
Classification: Other
Component: General
0.2.16
Other All
: Normal critical
: ---
Assigned To: Beagle Bugs
Beagle Bugs
: 417053 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-03-17 15:45 UTC by durand1
Modified: 2007-03-17 16:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description durand1 2007-03-17 15:45:47 UTC 
Please describe the problem:
Beagle indexer was running and it suddenly used the whole CPU at 100%. I had to kill it and the problem went away. A bit later, the system complained that I had run out of disk space. My Home folder is 8.8 GB and I rarely go beyond 2GB. So I ran Baobab, a disk usage analyser. This reported that there was 6 GB of data in the ~/.beagle/Log folder. I went there and was extremely surprised to see lots of logs, but what was weird was the fact that there were 2 huge files, one 2 GB and the other 4GB! It seems that beagle stopped working as it ran out of disk space. I immediately deleted both files because a lot of my porgrams were complaining. I forgot to screenshot the Log folder but I do have a screenshot of Baobab: http://img264.imageshack.us/my.php?image=screenshotdn7.png

Steps to reproduce:
I don't know how to reproduce this problem as I don't know what caused it. It might have been a recursive error or something like that.

Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Joe Shaw 2007-03-17 16:19:45 UTC 
Can you attach the first 1000 and last 1000 lines of the large log files?  0.2.6 is a very old release (the latest is 0.2.16) so there is a very good chance this bug is already fixed.

What distribution are you using?
Comment 2 durand1 2007-03-17 16:30:17 UTC 
oh oh, i cant attach any lines of the big log files because i had to delete them. I didnt have any space at all and many applications were complaining.
The version number is actually 0.2.16 but I couldnt select that one in the bug report.
Comment 3 durand1 2007-03-17 16:30:58 UTC 
oh and Im on Ubuntu Feisty Fawn
Comment 4 durand1 2007-03-17 16:40:43 UTC 
I guess that information isn't very useful :( I doubt it is a persistant problem so I just hope that it doesn't happen again or to anyone else...
Comment 5 Joe Shaw 2007-03-17 16:45:45 UTC 
That's unfortunate. :(

Can you please continue to run Beagle and update the bug if you do see it again?
A 6gb log file is obviously too large, and it indicates that you are hitting a bug that is looping over and over.  Those are the worst kind, so I'd like to find it and eliminate it.

If you are running 0.2.16, it is very likely you are seeing a problem with SVG files.  This was fixed in 0.2.16.1, I believe, and I know that 0.2.16.3 was just pushed into Feisty, so I'm hoping this problem is already fixed.

In any case, please do reopen if you see it again.
Comment 6 Joe Shaw 2007-03-17 16:48:57 UTC 
*** Bug 417053 has been marked as a duplicate of this bug. ***
Comment 7 durand1 2007-03-17 16:52:37 UTC 
yes, thats very probable, I've been working on svg files quite a lot recently. I'll update this if I re-encounter the problem again. Thanks!