I posted this problem originally on the xml group. I have an app that
processes XmlDocument and uses XmlElement.GetElementsByTagName quite
liberally for various operations. It appears that the XmlNodeList (actually a
subtree) returned by this method internally hooks itself to the document's
NodeInserted and NodeRemoved events. After a while, inserting an element into
the document takes close to 12 seconds on a PIII 1.8GHz 512MB machine because
each instance of the XmlNodeList is notified about the insertion.
All references to the XmlNodeList are only local variables with method scope.
Q1: Is there some way I can clear the listener collection of the
XmlDocument's events?
Q2: Does forcing a GC.Collect() help in these kind of cases?
I currently clone the XmlDocument at regular intervals to keep the
performance reasonable. This makes the app run 25 times faster.
many thanks,
Satish
GC.Collect will not help. It's kind of by design.
Also consider using XPathDocument instead as it solves this and other
problems.
>I posted this problem originally on the xml group. I have an app that
> processes XmlDocument and uses XmlElement.GetElementsByTagName quite
[quoted text clipped - 19 lines]
> many thanks,
> Satish
Sankar Nemani - 23 Aug 2004 22:40 GMT
You can use reflection to actually remove the handler(s). This approach
probably is not recommended but if you have no other choice you can use it.
> GC.Collect will not help. It's kind of by design.
> Also consider using XPathDocument instead as it solves this and other
[quoted text clipped - 23 lines]
> > many thanks,
> > Satish