Next step to try is to attach the debugger running PrjServer.exe process:
Find the PID of PrjServer.exe in the Process Explorer Find the TID of the thread that eats the CPU time Run cladb -p <pid> In the debugger open the Thread List window (main menu → Window → Thread List) Highlight the line for the thread with found TID Press the Ctrl-Space key to suspend selected thread and the press the Space key to show that thread’s in the Stack Trace window Right click on the most bottom upper-level node in the Stack Trace window and choose the Locate In Assembler item in the popup menu Make the height of the disassembler window as much as possible and provide the screenshot.
CODE
!Run('"C:\Clarion11\bin\Cladbne.exe"', 0) ! Loads Cladb
Glo:CurrentPID = ISWA_GetCurrentProcessId(0)
Message('Glo:CurrentPID = ' & Glo:CurrentPID)
Glo:DebuggerCommandLine = '"C:\Clarion11\bin\Cladbne.exe" -p ' & Glo:CurrentPID
Run(Glo:DebuggerCommandLine, 0) ! Does not "appear" to work
Glo:DebuggerCommandLine = '"C:\Clarion11\bin\Cladb.exe" -p ' & Glo:CurrentPID
Run(Glo:DebuggerCommandLine, 0) ! Works - Well you get the UAC prompt, but then ClaDB dissappears - Windows Defender possibly?
!Run('"C:\Clarion11\bin\Cladbne.exe -p ' & Glo:CurrentPID & '"', 0) ! Does not "appear" to work
!Run('"C:\Clarion11\bin\Cladbne.exe"', 0) ! Does not "appear" to work
!Run('"C:\Clarion11\bin\Cladbne.exe" -p' & Glo:CurrentPID, 0) ! Does not "appear" to work
Main()
Edit.