Windows error 0x00000229, 553

Detailed Error Information

PROFILING_AT_LIMIT[1]

MessageThe number of active profiling objects is at the maximum and no more may be started.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x80070229.

HRESULT analysis[2]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.
FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[2][1]
DescriptionThe default facility code.[2][1]
Error Code553 (0x0229)

Questions

0votes
1answer

The !address windbg command says that heap address is 'REGionUsageIsVAD' even though it was allocated using HeapAlloc

My heap buffer of interest was allocated as follows: 0:047> !heap -p -a 1d7cd1f0 address 1d7cd1f0 found in _DPH_HEAP_ROOT @ 5251000 in busy allocation ( DPH_HEAP_BLOCK: UserAddr UserSize - VirtAddr VirtSize) 1cf8f5b0: 1d7cc008 3ff8 - 1d7cb000 6000 68448e89 verifier!AVrfDebugPageHeapAllocate+0x00000229 76e465ee ntdll!RtlDebugAllocateHeap+0x00000030 76e0a793 ntdll!RtlpAllocateHeap+0x000000c4 76dd5dd0 ntdll!RtlAllocateHeap+0x0000023a 000ca342 TEST+0x0002a342 000be639 TEST+0x0001e639 As [...] read more
debugging
windbg

Comments

Leave a comment

(plain text only)

Sources

  1. winerror.h from Windows SDK 10.0.14393.0
  2. https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0