Excessive Size For The Current Operation
Application Verifier stop message
Heap violation detected. Excessive size of <size> bytes for the current operation.
Probable cause
This stop will be generated if in a HeapAlloc() or HeapReAlloc() operation the size of the block is above any reasonable value. Typically this value is 0x80000000 on 32-bit platforms and a larger value on 64-bit platforms. This stop also occurs when the allocation size is computed incorrectly, resulting in a negative number.
Information displayed by Application Verifier in Tool Window
Heap Handle - Heap handle for the heap owning the block
Block address – N/A
Size – N/A
Description - Heap violation detected. Excessive size of <size> bytes for the current operation
Trace description – No Stack Frame for the current block
Additional information
Check the current call stack where the block was allocated using either HeapAlloc() or Heap ReAlloc() with excessive size.
Frequency of this error is very low.