Facing an issue with Heap Corruption on a Specific Vmware Application

*************************************************************
* *
* HEAP ERROR DETECTED *
* *
**************************************************************

Details:

Heap address: 0000000002bc0000
Error address: 00000000479cce20
Error type: HEAP_FAILURE_BLOCK_NOT_BUSY
Details: The caller performed an operation (such as a free
or a size check) that is illegal on a free block.
Follow-up: Check the error's stack trace to find the culprit.


Stack trace:
0000000077a5dc1f: ntdll! ?? ::FNODOBFM::`string'+0x0000000000010c54
00000000777f1a4a: kernel32!HeapFree+0x000000000000000a
0000000074eacabc: msvcr90!free+0x000000000000001c
000000014036f4b1: vpxd!Vpxd::Vmprov::VmDirLayout::ComputeDestDirFile+0x0000000000000171
000000014036faac: vpxd!Vpxd::Vmprov::VmDirLayout::ComputeDestFilePath+0x000000000000006c
0000000140375aa7: vpxd!Vpxd::Vmprov::CopySpecBuilderBase::AddFileToNfcSpec+0x0000000000000167
00000001403767e4: vpxd!Vpxd::Vmprov::CopySpecBuilderBase::ProcessVmAuxFiles+0x00000000000002f4
00000001403773f4: vpxd!Vpxd::Vmprov::CopySpecBuilderBase::GenerateSpecs+0x0000000000000654
00000001403839bf: vpxd!Vpxd::Vmprov::ComputeSpecsImpl::Execute+0x000000000000026f
000000014035c6e6: vpxd!Vpxd::Vmprov::Workflow::Execute+0x00000000000001b6
000000014035da2b: vpxd!Vpxd::Vmprov::Workflow::StartWork+0x00000000000002eb
00000001402557bf: vpxd!VpxLRO::PreAndBodyStartWork+0x000000000000052f
0000000140259174: vpxd!VpxLRO::TryCatchVpxLROFuncExec+0x0000000000000024
0000000140267874: vpxd!VpxLRO::LroMainEntry+0x00000000000001d4
00000001402604e3: vpxd!VpxLRO::RunChild+0x0000000000000053
00000001402e7fc7: vpxd!VpxdVmprov::Migrate+0x0000000000000187

LFH Key : 0x0000002517967948
Termination on corruption : ENABLED
Heap Flags Reserv Commit Virt Free List UCR Virt Lock Fast
(k) (k) (k) (k) length blocks cont. heap \


Double free: This bug, where the same heap blocks are freed several times, is common in some applications. This is detected immediately by the page heap manager because, on the second free, the block will not have the proper prefix header and cannot be found among the allocated blocks. See Debugging Page Heap Failures for ways to analyze the stack trace of the first free operation. This error can be a variant of the reallocation problem because, when the application frees what it thinks it is the address of the block, that block was already freed as part of the reallocation.
ref: http://support.microsoft.com/kb/286470



!heap -a 0000000077a5dc1f

Index Address Name Debugging options enabled
1: 77a5dc1f
Unable to read _HEAP_SEGMENT structure at b70f00000004b941
Flags: ff418d19
ForceFlags: 03f88366
Granularity: 1224735609 bytes
Segment Reserve: 25048b48
Segment Commit: 00000db9
DeCommit Block Thres: 0d000012
DeCommit Total Thres: 251c8b48
Total Free Size: fe73c4e8
Max. Allocation Size: 0ffffe5641e9c032
Lock Variable at: e82024448948ffc9
Next TagIndex: 008b
Maximum TagIndex: 8d49
Tag Entries: 0000a888
PsuedoTag Entries: 7060ba0f
Virtual Alloc List: 77a5dd37
Unable to read nt!_HEAP_VIRTUAL_ALLOC_ENTRY structure at 8948fffff0002548
Uncommitted ranges: 77a5dd17
Unable to read nt!_HEAP_UCR_DESCRIPTOR structure at 1440ff4100000000
FreeList[ 00 ] at 0000000077a5dd77: 8348c9420f440000 . 008024848d480000
Unable to read nt!_HEAP_FREE_ENTRY struct