EXC_BAD_ACCESS KERN_INVALID_ADDRESS at 0x2c in CXMLElement

[conqueror]

We have used TouchXML in our app to parse XMLs coming from our backend.
In some circumstances app gives EXC BAD ACCESS in the following method:[CXMLElement attributeforName:]
Is there anyone who experienced this? I did not debugged it in detail yet but I think it is happening in xmlStrcmp(theLocalName, theCurrentNode->name) part.
More specifically in theCurrentNode->name.

while (theCurrentNode != NULL)
{
if (xmlStrcmp(theLocalName, theCurrentNode->name) == 0)
{
if (thePrefix == NULL || (theCurrentNode->ns
&& theCurrentNode->ns->prefix
&& xmlStrcmp(thePrefix, theCurrentNode->ns->prefix) == 0))
{
CXMLNode *theAttribute = [CXMLNode nodeWithLibXMLNode:(xmlNodePtr)theCurrentNode freeOnDealloc:NO];
return(theAttribute);
}
}
theCurrentNode = theCurrentNode->next;
}
return(NULL);
It is very hard to debug this because it happens randomly and it is not happening in all nodes. So let me know if you experienced this and there is a way to prevent this.
Thanks for your help in advance.

[RameshAran]

I am also facing this issue.

[RameshAran]

I just noticed that in Class "CXMLDocument", we are using "AutoReleasePool" in "dealloc" method as given below.

• (void)dealloc
  {
  // Fix for Add TouchXML.xcodeproj/xcuserdata/* to the .gitignore #35 http://code.google.com/p/touchcode/issues/detail?id=35 -- clear up the node objects first (inside a pool so I know they're cleared) and then freeing the document

  @autoreleasepool {
  nodePool = NULL;
  }
  //
  xmlUnlinkNode(_node);
  xmlFreeDoc((xmlDocPtr)_node);
  _node = NULL;
  }

Is this is the right way of memory management? I am not sure.