New
#1
Heap corruption was detected in heap 0x8bbfbe6d
I am in virtual enviroment and windows 7 32 bit in it.
I have my own .net windows application which is used to calculate sales.
after calculating week sales, when I try to print the document
when I print to toshiba printer, it is working fine and I dont have any issues.
when I print to HP printer from my application, my application crashes unexpectedly.
this happens randomly.
Below is the error:
Faulting application name: MyApplication.exe, version: *****, time stamp: 0x578e799c Faulting module name: ntdll.dll, version: ******, time stamp: 0x573a54ca Exception code: 0xc0000005 Fault offset: 0x00000000000438df Faulting process id: 0x22a8c Faulting application start time: 0x01cf4a1f36447f86 Faulting application path: C:\Program Files\MyApplication\MyApplication.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 3e2eb1a7-b615-10e3-bf1b-94a6h885c29
When I used the crash dump and debugged the application, I got the below result:
In App__PID__4120__Date__08_29_2016__Time_11_13_58AM__139__Second_Chance_Exception_C0000005.dmp the assembly instruction at ntdll!RtlpLowFragHeapFree+c5 in C:\Windows\System32\ntdll.dll from Microsoft Corporation has caused an access violation exception (0xC0000005) when trying to write to memory location 0x00000000 on thread 0 Heap corruption was detected in heap 0x94f5d000 However pageheap was not enabled in this dump. Please follow the instructions in the recommendation section for troubleshooting heap corruption issues. Current NTGlobalFlags value: 0x0
The finalizer thread is probably tring to release an instance of an STA COM component, and it is stuck waiting for the STA thread to become available. To resolve this problem, call Marshal.ReleaseComObject to clean up the references for all apartment-threaded COM components that you have used in your code deterministically (immediately), rather than waiting for the Finalizer Thread to do it at a later time.
Please help me how to solve the issue.
Quote