IDE debuggen und __Recovery?

[Kas Ob.]

@himitsu , in your second screenshot your focused thread is not the main one, yet it does show what may be the culprit,

LdrInitializeThunk is the kernel function responsible for loading dynamic libraries, most likely and like when the an exe is loading and the OS is preparing and loading its dependencies from its import table, some DLL loaded by LoadLibrary might pass without this, yet this one might be called for the import for that DLL, aka not directly.

On side note : i hate delayed loading import, it can lead to unpredictable cases.

Is there any thing useful with the main thread ? , as it is visible in the screen shot, which in a loop too, but with less intensive CPU usage at ~500 million cycle per second.
So your main thread might show the dead loop or at least more information.


extra resource:
https://stackoverflow.com/questions/...45012_43851743
, yet your case might be in loading and failed memory allocation, yet the main thread request loading again...

[himitsu]

OK, welcher Thread es war, war prinzipiell erstmal egal ... wollte nur wissen was da so viel CPU verbraucht
und ob ich da irgendeinen Anhaltspunkt finde, das Problem zukünftig zu beseitigen. (z.B. wenn es etwas von unserem eigenem DesignTimeCode gewesen wäre)
Ab und an sah dieser Thread z.B. so aus

Zitat:

0x0000000000000000
KERNELBASE.dll!VirtualQuery+0x23
0x0000000000000000
KERNELBASE.dll!VirtualQuery+0x23
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0x6a2
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0xefa
madExcept_.bpl!@Madstacktrace@StackTrace$qqrooop48 System@%DynamicArray$24Madstacktrace@TStackItem%p8 _CONTEXTpvoouiuit6ppvtctc56System@%DelphiInterface $29Madnvprgralert@IProgressAlert%uioo27System@%Ans iStringT$us$i0$%popuitltkp44System@%DynamicArrawqf FnTYk
SysDB280.bpl!@Ucimrtl@Exception@TCimExceptionHelpe r@GetExceptionMessageComplete$qqrv+0x102
rtl280.bpl!@System@Sysutils@Exception@RaisingExcep tion$qqrp23System@TExceptionRecord+0x1e
exceptiondiag280.bpl!@$xp$29Jclhookexcept@TJclModu leArray+0x683
rtl280.bpl!@System@@HandleAnyException$qqrv+0x35
ntdll.dll!RtlInterlockedCompareExchange64+0x1c4
ntdll.dll!KiUserExceptionDispatcher+0x26
madDisAsm_.bpl!@$xp$24Maddisasm@TPFunctionInfo+0x4 1ae
madDisAsm_.bpl!@Maddisasm@ParseCode$qqrpvr27System @%AnsiStringT$us$i0$%+0x8d1
madDisAsm_.bpl!@Maddisasm@ParseFunction_$qqrpvuit1 t1t1t1t1+0x3bf
madExcept_.bpl!@Madstacktrace@BcbTermination@$bctr $qqrx20System@UnicodeString+0x797
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0x1390
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0x175d
madExcept_.bpl!@Madstacktrace@StackTrace$qqrooop48 System@%DynamicArray$24Madstacktrace@TStackItem%p8 _CONTEXTpvoouiuit6ppvtctc56System@%DelphiInterface $29Madnvprgralert@IProgressAlert%uioo27System@%Ans iStringT$us$i0$%popuitltkp44System@%DynamicArrawqf FnTYk
SysDB280.bpl!@Ucimrtl@Exception@TCimExceptionHelpe r@GetExceptionMessageComplete$qqrv+0x102
rtl280.bpl!@System@Sysutils@Exception@RaisingExcep tion$qqrp23System@TExceptionRecord+0x1e
exceptiondiag280.bpl!@$xp$29Jclhookexcept@TJclModu leArray+0x683
rtl280.bpl!@System@@HandleAnyException$qqrv+0x35
ntdll.dll!RtlInterlockedCompareExchange64+0x1c4
ntdll.dll!KiUserExceptionDispatcher+0x26
madDisAsm_.bpl!@$xp$24Maddisasm@TPFunctionInfo+0x4 1ae
madDisAsm_.bpl!@Maddisasm@ParseCode$qqrpvr27System @%AnsiStringT$us$i0$%+0x8d1
madDisAsm_.bpl!@Maddisasm@ParseFunction_$qqrpvuit1 t1t1t1t1+0x3bf
madExcept_.bpl!@Madstacktrace@BcbTermination@$bctr $qqrx20System@UnicodeString+0x797
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0x1390
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0x175d
madExcept_.bpl!@Madstacktrace@StackTrace$qqrooop48 System@%DynamicArray$24Madstacktrace@TStackItem%p8 _CONTEXTpvoouiuit6ppvtctc56System@%DelphiInterface $29Madnvprgralert@IProgressAlert%uioo27System@%Ans iStringT$us$i0$%popuitltkp44System@%DynamicArrawqf FnTYk
SysDB280.bpl!@Ucimrtl@Exception@TCimExceptionHelpe r@GetExceptionMessageComplete$qqrv+0x102
rtl280.bpl!@System@Sysutils@Exception@RaisingExcep tion$qqrp23System@TExceptionRecord+0x1e
exceptiondiag280.bpl!@$xp$29Jclhookexcept@TJclModu leArray+0x683
rtl280.bpl!@System@@HandleAnyException$qqrv+0x35
ntdll.dll!RtlInterlockedCompareExchange64+0x1c4
ntdll.dll!KiUserExceptionDispatcher+0x26
madDisAsm_.bpl!@$xp$24Maddisasm@TPFunctionInfo+0x4 1ae
madDisAsm_.bpl!@Maddisasm@ParseCode$qqrpvr27System @%AnsiStringT$us$i0$%+0x8d1
madDisAsm_.bpl!@Maddisasm@ParseFunction_$qqrpvuit1 t1t1t1t1+0x3bf
madExcept_.bpl!@Madstacktrace@BcbTermination@$bctr $qqrx20System@UnicodeString+0x797
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0x1390
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0x175d
madExcept_.bpl!@Madstacktrace@StackTrace$qqrooop48 System@%DynamicArray$24Madstacktrace@TStackItem%p8 _CONTEXTpvoouiuit6ppvtctc56System@%DelphiInterface $29Madnvprgralert@IProgressAlert%uioo27System@%Ans iStringT$us$i0$%popuitltkp44System@%DynamicArrawqf FnTYk
SysDB280.bpl!@Ucimrtl@Exception@TCimExceptionHelpe r@GetExceptionMessageComplete$qqrv+0x102
rtl280.bpl!@System@Sysutils@Exception@RaisingExcep tion$qqrp23System@TExceptionRecord+0x1e
exceptiondiag280.bpl!@$xp$29Jclhookexcept@TJclModu leArray+0x683
rtl280.bpl!@System@@HandleAnyException$qqrv+0x35
ntdll.dll!RtlInterlockedCompareExchange64+0x1c4
ntdll.dll!KiUserExceptionDispatcher+0x26
madDisAsm_.bpl!@$xp$24Maddisasm@TPFunctionInfo+0x4 1ae
madDisAsm_.bpl!@Maddisasm@ParseCode$qqrpvr27System @%AnsiStringT$us$i0$%+0x8d1
madDisAsm_.bpl!@Maddisasm@ParseFunction_$qqrpvuit1 t1t1t1t1+0x3bf
madExcept_.bpl!@Madstacktrace@BcbTermination@$bctr $qqrx20System@UnicodeString+0x797
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0x1390
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0x175d
madExcept_.bpl!@Madstacktrace@StackTrace$qqrooop48 System@%DynamicArray$24Madstacktrace@TStackItem%p8 _CONTEXTpvoouiuit6ppvtctc56System@%DelphiInterface $29Madnvprgralert@IProgressAlert%uioo27System@%Ans iStringT$us$i0$%popuitltkp44System@%DynamicArrawqf FnTYk
SysDB280.bpl!@Ucimrtl@Exception@TCimExceptionHelpe r@GetExceptionMessageComplete$qqrv+0x102
rtl280.bpl!@System@Sysutils@Exception@RaisingExcep tion$qqrp23System@TExceptionRecord+0x1e
exceptiondiag280.bpl!@$xp$29Jclhookexcept@TJclModu leArray+0x683
rtl280.bpl!@System@@HandleAnyException$qqrv+0x35
ntdll.dll!RtlInterlockedCompareExchange64+0x1c4
ntdll.dll!KiUserExceptionDispatcher+0x26
madDisAsm_.bpl!@$xp$24Maddisasm@TPFunctionInfo+0x4 1ae
madDisAsm_.bpl!@Maddisasm@ParseCode$qqrpvr27System @%AnsiStringT$us$i0$%+0x8d1
madDisAsm_.bpl!@Maddisasm@ParseFunction_$qqrpvuit1 t1t1t1t1+0x3bf
madExcept_.bpl!@Madstacktrace@BcbTermination@$bctr $qqrx20System@UnicodeString+0x797
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0x1390
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0x175d
madExcept_.bpl!@Madstacktrace@StackTrace$qqrooop48 System@%DynamicArray$24Madstacktrace@TStackItem%p8 _CONTEXTpvoouiuit6ppvtctc56System@%DelphiInterface $29Madnvprgralert@IProgressAlert%uioo27System@%Ans iStringT$us$i0$%popuitltkp44System@%DynamicArrawqf FnTYk
SysDB280.bpl!@Ucimrtl@Exception@TCimExceptionHelpe r@GetExceptionMessageComplete$qqrv+0x102
rtl280.bpl!@System@Sysutils@Exception@RaisingExcep tion$qqrp23System@TExceptionRecord+0x1e
exceptiondiag280.bpl!@$xp$29Jclhookexcept@TJclModu leArray+0x683
rtl280.bpl!@System@@HandleAnyException$qqrv+0x35
ntdll.dll!RtlInterlockedCompareExchange64+0x1c4
ntdll.dll!KiUserExceptionDispatcher+0x26
madDisAsm_.bpl!@$xp$24Maddisasm@TPFunctionInfo+0x4 1ae
madDisAsm_.bpl!@Maddisasm@ParseCode$qqrpvr27System @%AnsiStringT$us$i0$%+0x8d1
madDisAsm_.bpl!@Maddisasm@ParseFunction_$qqrpvuit1 t1t1t1t1+0x3bf
madExcept_.bpl!@Madstacktrace@BcbTermination@$bctr $qqrx20System@UnicodeString+0x797
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0x1390
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0x175d
madExcept_.bpl!@Madstacktrace@StackTrace$qqrooop48 System@%DynamicArray$24Madstacktrace@TStackItem%p8 _CONTEXTpvoouiuit6ppvtctc56System@%DelphiInterface $29Madnvprgralert@IProgressAlert%uioo27System@%Ans iStringT$us$i0$%popuitltkp44System@%DynamicArrawqf FnTYk
SysDB280.bpl!@Ucimrtl@Exception@TCimExceptionHelpe r@GetExceptionMessageComplete$qqrv+0x102
rtl280.bpl!@System@Sysutils@Exception@RaisingExcep tion$qqrp23System@TExceptionRecord+0x1e
exceptiondiag280.bpl!@$xp$29Jclhookexcept@TJclModu leArray+0x683
rtl280.bpl!@System@@HandleAnyException$qqrv+0x35
ntdll.dll!RtlInterlockedCompareExchange64+0x1c4
ntdll.dll!KiUserExceptionDispatcher+0x26
madDisAsm_.bpl!@$xp$24Maddisasm@TPFunctionInfo+0x4 1ae
madDisAsm_.bpl!@Maddisasm@ParseCode$qqrpvr27System @%AnsiStringT$us$i0$%+0x8d1
madDisAsm_.bpl!@Maddisasm@ParseFunction_$qqrpvuit1 t1t1t1t1+0x3bf
madExcept_.bpl!@Madstacktrace@BcbTermination@$bctr $qqrx20System@UnicodeString+0x797
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0x1390
madExcept_.bpl!@Madstacktrace@InternalError$qqrx20 System@UnicodeStringoo+0x175d
madExcept_.bpl!@Madstacktrace@StackTrace$qqrooop48 System@%DynamicArray$24Madstacktrace@TStackItem%p8 _CONTEXTpvoouiuit6ppvtctc56System@%DelphiInterface $29Madnvprgralert@IProgressAlert%uioo27System@%Ans iStringT$us$i0$%popuitltkp44System@%DynamicArrawqf FnTYk
SysDB280.bpl!@Ucimrtl@Exception@TCimExceptionHelpe r@GetExceptionMessageComplete$qqrv+0x102
rtl280.bpl!@System@Sysutils@Exception@RaisingExcep tion$qqrp23System@TExceptionRecord+0x1e
exceptiondiag280.bpl!@$xp$29Jclhookexcept@TJclModu leArray+0x683
rtl280.bpl!@System@@HandleAnyException$qqrv+0x35
ntdll.dll!RtlInterlockedCompareExchange64+0x1c4

[himitsu]

Zitat von Kas Ob.:

thread is not the main one

https://embt.atlassian.net/servicede...tal/1/RSS-1224

But it could be that simple if we could see it directly.

[Kas Ob.]

Well, all what i see from this stack is
1) MadExcept may be unable handle exception (or to be more accurate,) can't stack tracing under low memory, unless it is failing to handle its own exceptions.
2) There is recursive calls and this is more dangerous then (1)
3) The stack is cut short, this is not all !, and you need more powerful tool to capture the stack on such thread, for that use WinDbg.