Debugging in Delphi is slow

Thank you for reaching out to the community forum.

May we know what version of MR your device is using now? I'd suggest checking the latest MR available from this page to see if this lists a higher MR version than you have applied currently.

Later releases will contain all previous fixes. If entering the latest "Windows Endpoint Platform Software Token: 8bd3ce50-84df-582c-bdc1-1250fd0c8c0f" displays a new version, this will keep you covered until the next major release which contains the fix you're looking for. 

Wanted to chime in here, this is still an issue. Confirmed that FTS 2023.2.1.28-MR2, which expires in 2 days, has whatever fix in it to keep HitManPro from causing the Delphi debugger to lag, but version FTS 2024.2.2.14.1-MR2 (which I think is most current) does not have the fix in it. Please advise when this fix might get rolled into a current MR, or a more recent MR that may contain this fix. Thanks!

Wanted to chime in here, this is still an issue. Confirmed that FTS 2023.2.1.28-MR2, which expires in 2 days, has whatever fix in it to keep HitManPro from causing the Delphi debugger to lag, but version FTS 2024.2.2.14.1-MR2 (which I think is most current) does not have the fix in it. Please advise when this fix might get rolled into a current MR, or a more recent MR that may contain this fix. Thanks!

Hello Chris, 

Thank you for reaching out to the community. This topic has been discussed Previously on other community threads sophos hitman pro alert und borland delphi debugging extrem lamngsam  

I can confirm that the hotfix for this performance issue has already been pushed to the latest FTS FTS 2024.2.2-MR2.

Hi Glenn, Thanks for the quick reply.

Do you have a token for the specific 2024.2.2 version where this is fixed? It is currently not fixed working in 2024.2.2.1.0 (recommended, which is installed for other developers with the same issue) or 2024.2.2.14.1-MR2 (the version I tried before the expiring version). 

If the latest hotfix packages have already been tried but this issue continues to persist, I'd suggest proceeding with the Product Analysis steps using the Endpoint Self Help tool. 
- Product Analysis Tool

This will help determine if the issue remains the very same, or if other components may be affecting the results you're seeing. 

Hi Kushal,

I am working on opening a ticket with support after running the analysis tool you suggested, thanks. 

For documenting the issue further, I updated to FTM 2024.2.2.6.1-MR1, with the issue returning after update. I did notice, I believe, the expiration date on 2023.2.1.28-MR2 was pushed back to October 1.

As noted in the original German post, the issue appears to be hmpalert.exe, which spikes on my PC to 8% CPU usage on each debug step in the Delphi IDE. Using the analysis tool, turning off all Sophos features does not solve the issue, but removing tamper protection and stopping the HitmanPro.Alert Service does make the issue go away. 

I appreciate all the help!

does this help you to exclude the debug executable from HMPA scanning?

community.sophos.com/.../how-to-exclude-application-from-hmpa-dllhijackguard

Hello,

since FTS 2023.2.1.28-MR2 expired today: is the fix regarding the slow-down problems with debugging in Lazaraus/Delphi already integrated into the normal release? Or which software version do we need to assign to affected machines?

Per Sophos Support, the resolution for this issue that worked for us was to explicitly exclude the bds.exe executable from scanning.

We created a "File or Folder (Windows)" exclusion pointed at "C:\Program Files (x86)\Embarcadero\Studio\22.0\bin\bds.exe" [if your version is different, the 22.0 might be a different number] for "Real time and scheduled" scanning.

We had already created an exclusion for the parent folder, but according to the support tech, while this will ignore file access, it won't make Sophos ignore any processes launched from that folder. So you have to exclude the executable directly so Sophos 100% ignores it.

There was no need for a specific version or MRT.

Hello,

thanks for the information. Since there exists a fix for this problem, we would like to get a permanently fixed version and not create exclusions. Also this exclusion did not work for us.

 Qoosh or GlennSen do you have an update or reply?

BR