Slickedit tagging hangs on SystemVerilog project

[Paul]

I'm running VS on Windows 11 25H2.

I've been using VS2023 up until recently without issue. Starting with 2025 Hotfix 2 (I'm not sure about before) I noticed VS would have high CPU usage when I wasn't doing anything. If I closed it I could still see it in task manager using the same amount of CPU and I would have to kill it. I turned off background tagging and that solved that problem. But when I actually try to tag a SystemVerilog project (that I have been using for over a year with 2023) it seems to hang at around 11-13%. The file listed at that time is different every time. There are over 9000 files in my project. I've tried running with and without "Generate References" checked. What steps can I take to help debug this further? I can't provide any files (all work product) but perhaps there is a way to get some debug info so I could trace the problem to a specific SV construct or memory leak or some other issue related to the size/number of tags, etc.

[Clark]

Try using Project>Retag Workspace

Turn off "Retag files in background when possible". Assuming SlickEdit is having a problem parsing a specific file, this should help determine which file. Although, not every filename gets displayed before it is parsed. You should be able to notice about where SlickEdit hangs. Worst case you can create a temporary project and narrow the search down by removing project files until SlickEdit can finish.

I was hoping there was a good debug logging option you could turn on but there isn't one.

Once you know what file is the problem, I suspect you can create a similar non-proprietary source file and email the sample file to support.

[pmsteinm]

I realized I wasn't logged in when posting the above items. Now that I am I can't edit the above. I meant to add above that "just pasting the contents below into an empty SV file causes an immediate hang of VS."

Also that the file I found was added over the break. So this might not be a VS 2025 hf2 specific problem.

[Clark]

Reproduced. Definitely not a new problem. We will post when we have a fix.

[Clark]

We have built a new Win64 installer with a fix for this:

Go to this dropbox folder:
https://www.dropbox.com/scl/fo/oiizbih4j3hpqcs9uqfuz/AIftZrn-xdFUsd-Jkhqai4U?rlkey=mbhzr21who40mdb96bt3s60xb&st=f35teo0j&dl=0

And download se_30000000_win64-2026-01-09.msi

This fix will be included in v30.0.1. No date set yet but should be no later than sometime in March

[pmsteinm]

The real RTL file works fine with the new install. Thanks.