To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=49572
------- Additional comments from [EMAIL PROTECTED] Fri May 20 06:35:00 -0700 2005 ------- The attached stacks show three different possible leaks: 1. Stacks that involve expat All leaked strings are passed as character data callbacks. An initial look at the code in both sax and configmgr/source/xml/basicparser.cxx does not reveal any leaks. All string handling is done through properly scoped OUString objects. I'll check later in a debugger, if the string buffers live on in configmgr to a place where they might be leaked. The other alternative would be a code generation error (probably in sax) that causes temporary objects to leak. 2. Stacks that involve bootstrapcontext.cxx:127 That line allocates a rtl::Bootstrap handle. Looking at the code in rtl, it appears that the Bootstrap_Impl structures with the associated data are cached in a static map to avoid repeated file parsing. Stacks appear to be incomplete, but strings allocated under that stack are probably bootstrap parameter values and at least one of the stacks reports a leaked Bootstrap_Impl structure. The Bootstrap_Impl structures are reference counted, but I see no obvious reason why configmgr should be responsible for them being leaked, unless entire configuration views are leaked by clients. The latter is also possible, particularly because utl::ConfigItems are kept alive in a staic map and may never be released. 3. The last stack shows a leak in something allocated by gconf called by the system integration gconf-backend. If this needs to be fixed it should be a separate bug. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
