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 363744 - Beagle uses infinitive amounts of memory
Beagle uses infinitive amounts of memory
Status: RESOLVED DUPLICATE of bug 348139
Product: beagle
Classification: Other
Component: General
0.2.9
Other Linux
: Normal blocker
: ---
Assigned To: Beagle Bugs
Beagle Bugs
Depends on:
Blocks:
 
 
Reported: 2006-10-20 19:51 UTC by Bengt Lüers
Modified: 2006-10-25 20:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bengt Lüers 2006-10-20 19:51:37 UTC 
Some people using Ubuntu Edgy Eft from the ubuntuusers.de-forum complain about beagle using huge amounts of memory (>400MB) after running properly for about 30 minutes.

I cannot repuduce this, although I am using Edgy, also.
Since that fact, I can not offer any informations. Anybody else?
Comment 1 Joe Shaw 2006-10-20 19:56:10 UTC 
If they have large thunderbird mailboxes, it could be bug 355549.

You can try running beagled with "--deny-backend thunderbird" and see if that improves the situation.
Comment 2 Bengt Lüers 2006-10-20 20:04:25 UTC 
He thx so far, I will report that.

Here are some more informations:
To be exact it is all about, the beagled-helper.
It uses 100% CPU-time while growing bigger and bigger.
The problem also appeared with Dapper Drake recently, too.
Comment 3 Joe Shaw 2006-10-20 20:13:19 UTC 
Oh, ok, if it's the helper, then it's not the Thunderbird backend.  It's a specific piece of data which is causing problems.  I would need the output from the ~/.beagle/Log/current-IndexHelper file to know which file was causing the problem, and then I'd need a copy of the file to fix it.
Comment 4 Bengt Lüers 2006-10-24 16:36:42 UTC 
Hey finally I got the problem agin. The beagled-helper seems to use all my machine'S power to solve an unsolvable problem. It brings my CPU to 100% load and the ~/.beagle/Log/current-IndexHelper-File does not have changes in three tries within quarter an hour.

Here is the last line of the Log:

061024 1816273129 12780 IndexH DEBUG: +file:///home/bengt/Media/Backup/Backups/Mozilla Tunderbird/chrome/classic.jar

I gonna move this thing to another partition and restart to see if this breakdown is reproduceable.
Comment 5 Joe Shaw 2006-10-25 20:39:58 UTC 
Ok, this bug was fixed in version 0.2.10.

*** This bug has been marked as a duplicate of 348139 ***