When I was looking at some existing code in a K2 solution at work I noticed a reference to an XML parser. My boss told me to investigate this as he thinks that XML parsers can be unstable (memory leaks?)... I was wondering if anyone would be able to give me more clue as to what sort of parser this is and whether it is unstable or not. Unfortunately I can't find the reference for the parser anymore so even if someone could tell me what the inbuilt parser is then that would help me with my research.

 TIA

You probably want to post the full reference (name of DLL or its namespace) to the parser so we know what you are referring to.

Could it be the K2Utilities.dll you are referring to?  If so, it is used internally by K2 processes and includes a class that is used for getting and setting process/activity xml field values.  It is used extensively by numerous K2 events etc. and is stable.  I'm not aware of K2 xml parser so if you can post the dll name or namespace as Peter points out, it would help.

---

The statements and opinions made in my postings are my own, and do not reflect the opinions of SourceCode Technology Holdings, Inc. or its subsidiaries. All information is provided as is with no warranties, express or implied, and grants no rights or licenses.

I have found the reference to XML again now. It turns out this is in the SourceCode.K2Utilities package/namespace so I assume tha's what you were talking about...

Are you saying this is quite stable and is unlikely to be the cause of any problems I have?

That's kind of vague.  Are you having some specific problems that you think are related to XML parsing? 

---

The statements and opinions made in my postings are my own, and do not reflect the opinions of SourceCode Technology Holdings, Inc. or its subsidiaries. All information is provided as is with no warranties, express or implied, and grants no rights or licenses.

Sorry, I know it's vague, but I don't have any idea what I'm talking about. My boss just said "Oh, XML Parsers, they can have memory leaks"... Useful, no? :-P

We do have a memory leak somewhere within the application that uses K2, but I really doubt that it's related to this. We have gone over the recommended 2000 site limit in SharePoint and this seems much more likely as the cause.

I don't know if someone would mind commenting on any known stability issues with the XML parser just so I have something to tell him? Obviously if there are no issues then then that's even better. :)

The K2Utilities.dll component is used internally by K2 processes in several places and there are no known issues with it.  If you suspect there is a memory leak in your applicaiton that uses K2, I doubt it is related to K2Utilities.dll.  If you suspect the K2 Server is leaking memory I would recommend opening a support ticket.

---

The statements and opinions made in my postings are my own, and do not reflect the opinions of SourceCode Technology Holdings, Inc. or its subsidiaries. All information is provided as is with no warranties, express or implied, and grants no rights or licenses.

Thanks, that should be enough to report. For reference, I don't think the memory leak is from K2.