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 353618 - beagled-helper uses 800 MB of memory
beagled-helper uses 800 MB of memory
Status: RESOLVED DUPLICATE of bug 348139
Product: beagle
Classification: Other
Component: General
0.2.8
Other All
: Normal critical
: ---
Assigned To: Beagle Bugs
Beagle Bugs
Depends on:
Blocks:
 
 
Reported: 2006-08-30 23:41 UTC by alejandro vera
Modified: 2006-08-31 18:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
this are the logs since yesterday (878.57 KB, application/x-compressed-tar)
2006-08-30 23:43 UTC, alejandro vera
Details

Description alejandro vera 2006-08-30 23:41:12 UTC
Please describe the problem:
some days ago I submited bug 353327. This is a dup of bug 348139

Last night i left my notebook with beagled-helper using 100% of the cpu. 

Today (24 hours later) this is the result of 'top'. Last night the numbers where  about 128 MB


top - 19:36:06 up 1 day, 32 min,  2 users,  load average: 1.69, 1.73, 1.54
Tasks:  95 total,   3 running,  92 sleeping,   0 stopped,   0 zombie
Cpu(s): 96.3%us,  3.3%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.3%hi,  0.0%si,  0.0%st

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 7142 alejo     15   0  847m 534m 509m S 62.0 109.5   1093:39 beagled-helper
14406 alejo     17   0  9872 6260 1608 R 10.9  1.3   0:00.33 spamassassin
 4181 root      16   0  181m  34m 8772 R  9.3  7.1  11:32.89 Xorg
 5739 alejo     15   0 34776  11m 8196 S  7.3  2.4   1:23.46 gnome-terminal
 4673 alejo     15   0  316m 103m  19m S  7.0 21.2  30:04.40 firefox-bin
 4287 alejo     15   0 16960 8568 6536 S  2.0  1.7   0:17.54 metacity
 6300 alejo     16   0  2232 1056  828 R  0.7  0.2   4:04.14 top
 4335 alejo     16   0 24164  10m 8200 S  0.3  2.2   1:41.91 wnck-applet
11778 alejo     15   0  129m  28m  14m S  0.3  5.8   0:58.35 evolution-2.6
    1 root      15   0  1936  576  548 S  0.0  0.1   0:01.72 init
    2 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/0
    3 root      34  19     0    0    0 S  0.0  0.0   0:00.36 ksoftirqd/0
    4 root      10  -5     0    0    0 S  0.0  0.0   0:00.12 events/0
    5 root      10  -5     0    0    0 S  0.0  0.0   0:00.00 khelper


Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
I didn't touche the computer since last night so it is not a result of my interaction.

I hope to be helpful
Comment 1 alejandro vera 2006-08-30 23:43:15 UTC
Created attachment 71940 [details]
this are the logs since yesterday
Comment 2 Debajyoti Bera 2006-08-30 23:52:05 UTC
I see this in the logs:
060829 1906219899 04325 Beagle ERROR EX: Unable to start EvolutionDataServer backend: Unable to find or open libraries:
060829 1906219899 04325 Beagle ERROR EX: System.DllNotFoundException: libecal-1.2.so.3

Probably EDS is not properly installed ? beagled is not able to find libecal-1.2.so.3
Can you disable EDS backend and check if there is any leak ?
Comment 3 alejandro vera 2006-08-31 01:09:58 UTC
Ok. i am going to remove the beagle-backend-evolution

i have libecal-1.2.so.6 but not .3

Now i'll wait until tomorrow to see if the leak is present
Comment 4 Joe Shaw 2006-08-31 18:08:00 UTC
  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 7142 alejo     15   0  847m 534m 509m S 62.0 109.5   1093:39 beagled-helper

First, VIRT isn't a good indication of the memory being used.  RES is closer, but the odd thing is that SHR is also a huge amount.  Generally, you can find out real memory usage by doing RES - SHR which equals in this case 25 megs.  Bizzare.

Running pmap on the process and attaching the output might be helpful.
Comment 5 Joe Shaw 2006-08-31 18:14:21 UTC
Memory usage aside, it is taking forever on javascript files, which makes it look like a dup of bug 348139.

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