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 335560 - beagle leaks over 1gb of memry
beagle leaks over 1gb of memry
Status: RESOLVED DUPLICATE of bug 335178
Product: beagle
Classification: Other
Component: General
0.2.3
Other All
: Normal critical
: ---
Assigned To: Beagle Bugs
Beagle Bugs
Depends on:
Blocks:
 
 
Reported: 2006-03-22 19:40 UTC by alejandro vera
Modified: 2006-03-22 20:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
The log when beagled leaked memory (116.79 KB, text/plain)
2006-03-22 19:58 UTC, alejandro vera
Details

Description alejandro vera 2006-03-22 19:40:31 UTC
Please describe the problem:
I installed beagle in debian sid. 0.2.3

I deleted my old indexes and started beagled from fresh instalation

Many hours later i created a text file and when i saved it my HD began to work
like crazy and i lost responsivity of my box. I had to ssh from other notebook
to mine and find that beagle was using 1080 Mb of virtual memory. i managed to
kill the process "beagled" and all become normal again

I'll attach the log in the next message. it is full of warnings and other kind
of error.

If someone is interested in this bug (please!!!) then it could be useful to look
the logs i attached to bug 335272 

Steps to reproduce:
1. let beagle run many hours
2. create and save a text document with some words

I now it not fill fail always.. it is what I did :(

Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 alejandro vera 2006-03-22 19:58:53 UTC
Created attachment 61788 [details]
The log when beagled leaked memory

This is the log ... it has lots of errors..

the more strange error is that are a lot of references to /home/jose or /home/something in the stack trace... i asume that are from the packager from debian...
Comment 2 Debajyoti Bera 2006-03-22 20:09:59 UTC
There is another bug of similar kind. Please add further comments there. Helps in seeing all comments at the same place.

One thing I noticed in the log files of these bugs is some exception occuring down the line, which basically stalls the indexing process. However as crawling continues, the to_index queue keeps getting longer and longer. That might be one reason for the memory blowouts.

/home/jose is just the packager. Can you try building the source yourself ? There are a lot of unusual errors. Some even strange one! Can you also delete (probably a file) /usr/lib/beagle/Backends ?



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