Maximum Call Stack size Exceeded - Print Function

A A BIZACA 1

Hi, I have a problem with Azure Data Studio."Maximum Call Stack size Exceeded"
This happens when i print each record to output window. There seems to be a limit to how many times i can print the result to output window...

----------------

Query Sample

----------------

declare @CNT int = 1

while @CNT <= 130000
begin

print @CNT

set @CNT = @CNT + 1
end

Run this query and see for yourself - if you change the value 130 000 to example 100 000 it works fine. Otherwise you get the call stack error.

So my question is: Can you increase that limit somehow in Azure Data Studio?

That same query runs perfectly in SQL Management Studio

Dan Guzman 9,211 Reputation points

2021-03-15T15:58:37.717+00:00

FWIW, I don't get such an error with ADS 1.26.1 but the number of messages are truncated. Consider reporting the issue on feedback. 100K+ print messages seems an uncommon use case to me.
Navtej Singh Saini 4,221 Reputation points Microsoft Employee

2021-03-16T00:50:35.657+00:00

@A A BIZACA

We see that you have raised the issue with support through the twitter handle. They shared a link which may not be working for you, so we are sharing it again.

Please check and confirm it is working for you and share the ticket number.

Regards
Navtej S
A A BIZACA 1 Reputation point

2021-03-16T08:09:43.95+00:00

Ok, please try the following:

Run that query again until it completes.

Open n new query window, then navigate to that first query that was completed.

You will then see the "Unable to open 'SQLQuery_1 - sqldev...grated)': Maximum call stack size exceeded." error on the bottom left.

It also erases the query text.
A A BIZACA 1 Reputation point

2021-03-16T08:20:04.817+00:00

Here is the gitHub link

https://github.com/microsoft/azuredatastudio/issues/14744
Navtej Singh Saini 4,221 Reputation points Microsoft Employee

2021-03-16T16:05:17.907+00:00

@A A BIZACA Thanks for creating the issue on the Github. We will wait on the team to respond or will try to get the traction for the issue. We appreciate your patience in this regard.

Thank you
Navtej S
Navtej Singh Saini 4,221 Reputation points Microsoft Employee

2021-03-27T00:45:21.73+00:00

@A A BIZACA Team has been able to reproduce this and working on the workaround or the fix now.

1 answer

Navtej Singh Saini 4,221 Reputation points Microsoft Employee

2021-03-29T23:57:49.657+00:00

@A A BIZACA - The confirmed that it is the bug and the issue fix has been applied and latest build can be downloaded from here.

Please let us know if you need further help.

Regards
Navtej S
Please sign in to rate this answer.

0 comments No comments
Sign in to comment