CLR SP debugging problem

Hi All,

Could you please help me?

I have a problem with T-SQL stored procedure, which call the CLR Stored Procedure, and when it runs into it my Visual Studio gets berserk, looping like crazy, eating 100% CPU and gobling off more and more memory. The Visual Studio out into the the Output window the following message over and over again:

WARNING: Debugger was accessing T-SQL variables while managed code was not suspended. Waiting until the access is done to continue T-SQL execution.Continueing T-SQL execution.

WARNING: Debugger was accessing T-SQL variables while managed code was not suspended. Waiting until the access is done to continue T-SQL execution.Continueing T-SQL execution.

The only way to stop it is by killing the Visual Studio process. Then I have to stop, or sometimes even kill the SQL server to bring the CPU down from 100%.

What should I do to avoid this problem? Thank you very much for the help.

Does this problem reproduce consistently? This is likely to be a known issue with debugging while in parallel execution. Can you try setting MAXDOP(1) and see if that solves the problem?

If not, can you paste the code you're using that's hitting this?

Thanks,

Steven

|||

The problem was in the test data. My CLR procedure processes regular expressions. The pattern for regular expression has been written incorrectly and because of it there was an error in debug process. After I have corrected a pattern of regular expression a problem have left.

Thank you for the consideration,

Sveta