[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xerces-c-dev
Subject:    RE: Application stuck in creating XercesDOMParser object
From:       "Mollyn, Priya" <pmollyn () cisco ! com>
Date:       2006-03-17 3:18:54
Message-ID: 03772D1EC8DE624A863058C75874A75CCDF515 () vtg-um-e2k6 ! sj21ad ! cisco ! com
[Download RAW message or body]

Thank you for the prompt reply. Yes, we are creating and destroying
DOMParser object instance everytime we need to parse a xml. We will try
the change you suggested to reuse the DOMParser object and see if that
helps.

Thanks
-Priya 

-----Original Message-----
From: David Bertoni [mailto:dbertoni@apache.org] 
Sent: Thursday, March 16, 2006 5:47 PM
To: c-dev@xerces.apache.org
Subject: Re: Application stuck in creating XercesDOMParser object

Mollyn, Priya wrote:
> Hi,
>  
> We are using Xerces C++ Parser 2.6 version, and are noticing high cpu 
> issue, and when we attach gdb, it is pointing to malloc in 
> XercesDOMParser object creation. Has anyone seen this issue ? Any idea

> on how to fix this ? The issue is intermittent, not easy to reproduce,

> but so far happened couple of times already. Once this issue happens, 
> the process seems to be stuck doing nothing.
>  
> Any help would be appreciated.
>  
> 
> (gdb) where
> 
> #0  0x005fd304 in malloc_consolidate () from /lib/tls/libc.so.6
> 

This looks like the memory manager is spending time consolidating the
heap, which indicates your application is suffering from heap
fragmentation.

It's difficult to know how you could fix this problem without knowing
the details of how your application, and that's beyond the scope of this
mailing list.

If you are creating and destroying lots of XercesDOMParser and DOM
instances, you might try caching these instances and reusing them, to
see if that helps.

On the other hand, the fragmentation could be caused by something in
your application which is not at all connected to Xerces-C.

Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]