Using the "Stepping Into" debug tool along with breakpoints in Scripts that use "stateful iterators" cause random CorePackage Localization scripts to be opened for editing in studio

What issue are you having? Describe what is happening when the bug occurs.

https://gyazo.com/8bff2f3ddcc8dba408b59d74e32bdbb9

While trying to use the “Step Into” debugging feature for breakpoints in a script that uses “stateful iteration,” as the roblox wiki calls it, random scripts that appear to be related to the Localization Text Capture tool automatically pop up in my script editor and the debugging tool is applied to those scripts instead while they are running. These scripts don’t reveal crucial info but they are an annoyance and I can’t debug my original script without the Localization scripts popping up.

Does the bug happen 100% of the time?
yes

If so, are there steps that reproduce the bug?
Create a script in workspace, and paste the following code:

function test()
return 1
end
for val in test do
wait()
end

  1. Set a breakpoint anywhere except the last line of the script
  2. Keep pressing the Step Into button in the debugger

Where does the bug happen? (www, gametest, etc) What type of platform are you on? (Mac, PC, Android, iOS, XBox, etc) Which OS and version are you using?
Roblox Studio bug, Windows 10

Is it level-specific? Is it game specific? Please post a link to the place that exhibits the issue.

Anything else that you would want to know about the bug if it were your job to find and fix it.

  • This only appears to occur when I use stateful iterators (Documentation - Roblox Creator Hub)

  • The Localization script that the debugger goes to keeps repeating a function of code when I press Step Into a bunch of times, so it may be related to the Text Capture/scraper tool

  • The scripts that pop up are in CorePackages (seen in Call Stack)

4 Likes