Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 216863 - memory leak/high memory usage in beagle over a long period of time
Summary: memory leak/high memory usage in beagle over a long period of time
Alias: None
Product: Fedora
Classification: Fedora
Component: beagle
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: David Nielsen
QA Contact:
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2006-11-22 13:11 UTC by Edmond Hui
Modified: 2008-05-06 16:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-06 16:54:51 UTC

Attachments (Terms of Use)

Description Edmond Hui 2006-11-22 13:11:15 UTC
Description of problem:

It seem like there is a memory in beagle, noticed memory usage increase over
time (~7 hours). beagled takes over 50% of 1GB on my T30. The setup is default,
with the button on panel to provide easy access. firefox is running but idle (I
keep my laptp on when sleeping, and found the memory lost when wake up).
beagle-shutdown releass some of the memory, or so it seems (no sure all are

Please advice what logs needed (and how to collect).

Comment 1 Alexander Larsson 2006-11-22 14:19:41 UTC
Mono memory use can be tracked with heap-buddy.
However, its unlikely I will be able to help you, its better to talk to upstream
directly about issues like this.

Comment 2 Edmond Hui 2006-11-22 14:29:22 UTC
you mean directly with beagle developer? If so, I can take a look later.


Comment 3 Alexander Larsson 2006-11-23 09:28:39 UTC
Yes, thats what i mean. In free software terminology the distributor is called
downstream, and the original author is called upstream. Bits flow from upstream
to downstream.

Comment 6 Bug Zapper 2008-04-04 04:52:07 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out

Comment 7 Bug Zapper 2008-05-06 16:54:50 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.