|
We are seeing some inconsistent behavior with V2.5. Every
few minutes the process using the parser will crash. We finally tracked it down
to XMemory new operator and so on…. If we use the debug build everything
works fine. But with release build, we just can’t make it to work. Here
is the call stack leading upto exception.. 845e7a4 77fcd039 004f0000 08267000 0845e7d0
ntdll!RtlpCoalesceFreeBlocks+0x10c 0845e7dc 77fccdc1 004f0001 00004058 00000000
ntdll!RtlpExtendHeap+0x1c1 0845e9b8 780010a8 004f0000 00000000 00004050
ntdll!RtlAllocateHeap+0x3b6 0845e9f8 78001045 00004050 780026df 00004050
MSVCRT!_heap_alloc+0xed 0845ea00 780026df 00004050 00000001 1205d841
MSVCRT!_nh_malloc+0x10 0845ea0c 1205d841 00004050 00000000 004f66f0 MSVCRT!operator
new+0xb WARNING: Stack unwind information not available. Following
frames may be wrong. 0845ea38 12021274 00004050 004fd130 12109d82
xerces_c_2_5_0!xercesc_2_5::MemoryManagerImpl::allocate+0x31 0845eaac 12109f1c 0845eac8 004fd0a4 004fd098 xerces_c_2_5_0!xercesc_2_5::XMemory::operator
new+0x14 0845eaf4 10001894 004fd0a4 0845eef3 004fcf18
xerces_c_2_5_0!xercesc_2_5::DOMWriterImpl::writeToString+0x5c |
