memory leak (about 100K) every time when I refresh remote datasource of xul:tree element

RESOLVED EXPIRED

Status

RESOLVED EXPIRED
15 years ago
3 months ago

People

(Reporter: alex, Assigned: mozilla)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7

I wrote application using Mozilla XUL technology. One of the parts of
application is tree with remote datasource. I refreshes datasource with next
code every 5 min:
function refreshlog2() {
  var tree;
  netscape.security.PrivilegeManager.enablePrivilege("UniversalXPConnect");
  tree = document.getElementById("MyTree");
    var datasources = tree.database.GetDataSources();
    while(datasources.hasMoreElements())
    {
        var currDS = datasources.getNext();
        var remote =
currDS.QueryInterface(Components.interfaces.nsIRDFRemoteDataSource);
        remote.Refresh(false);
    }
}
Every refresh causes growing memory used by MozillaFirebird.exe by 100K-200K
byte, however number of records in the tree still the same and not changed.
Also on the server side I use mod_gzip, so may be problem here.

Reproducible: Always

Steps to Reproduce:
1.Create simple tree
2.Populate it with remote datasource
3.Refresh it using code above.
4.On the server side I use mod_gzip, not sure about influence of it.
Actual Results:  
growing memory used by MozillaFirebird.exe

Expected Results:  
use same memory amount in case when datasorce have same size
This is not the right place to get help with custom applications.  I'm not sure
what you're doing wrong, but this is for problems with Mozilla Firebird itself.

you might want to try the mozdev.org forums/mailing lists or #mozilla on
irc.mozilla.org if you want help tracking this down.

IIRC, you need to trash the contents of the tree first, then refresh the data,
but its been a while since I dealt with this type of issue.

-> INVALID, not a bug found in the Mozilla Firebird product.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID

Comment 2

15 years ago
Reopening: this bug is valid, but in a wildly incorrect product/component.  This
is a Browser bug in RDF.
Status: RESOLVED → UNCONFIRMED
Component: General → RDF
Product: Firebird → Browser
Resolution: INVALID → ---
Version: unspecified → Trunk

Updated

15 years ago
Assignee: blake → rjc
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago13 years ago
Resolution: --- → EXPIRED

Updated

3 months ago
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.