Cannot use ctrl+enter to excute code in some situations

System details:

Positron and OS details:

Positron Version: 2025.04.0 (user setup) build 250
Code - OSS Version: 1.98.0
Commit: 627b3d723ee0b3a5bd86731a75902d419cafe22d
Date: 2025-04-03T16:50:39.209Z
Electron: 34.2.0
Chromium: 132.0.6834.196
Node.js: 20.18.2
V8: 13.2.152.36-electron.0
OS: Windows_NT x64 10.0.26100

Interpreter details:

sessionInfo()
R version 4.4.2 (2024-10-31 ucrt)
Platform: x86_64-w64-mingw32/x64
Running under: Windows 11 x64 (build 26100)

Matrix products: default

locale:
[1] LC_COLLATE=Swedish_Sweden.utf8
[2] LC_CTYPE=Swedish_Sweden.utf8
[3] LC_MONETARY=Swedish_Sweden.utf8
[4] LC_NUMERIC=C
[5] LC_TIME=Swedish_Sweden.utf8

time zone: Europe/Stockholm
tzcode source: internal

attached base packages:
[1] stats graphics grDevices utils
[5] datasets methods base

loaded via a namespace (and not attached):
[1] compiler_4.4.2 cli_3.6.3
[3] tools_4.4.2 rlang_1.1.4
[5] sessioninfo_1.2.3

Describe the issue:

This is the issue that I have problems with the most. I often run the code line by line using ctrl+enter. When I run something that takes a bit longer (i.e more than I few seconds) I find that I cannot press ctrl+enter to get to the next line until the previous code is finished.

This is of course frustrating when you want to keep going down while you wait for the original code to finish.

It seems to happen when there is some computation that takes a little more time than, say, normal data wrangling. Like running a regression.

It was not so easy to capture, but I managed to in this short clip. You can see that I try and press ctrl+enter several times until it finally bugs out. I should note that this is something that happens in just about every session for me.

https://github.com/user-attachments/assets/5fc98eec-5aaf-4ad2-8392-a7bb2d4fc843

Steps to reproduce the issue:

See above

Expected or desired behavior:

Were there any error messages in the UI, Output panel, or Developer Tools console?

Not that familliar with Developer Tools, but I think that maybe this is related?

No source file or test is named. Start by reproducing the report in Positron with an R computation that runs for several seconds, pressing Ctrl+Enter on subsequent lines while it runs, and inspect the Developer Tools output referenced in the issue. Done means the Ctrl+Enter behavior during a long-running computation is understood and corrected.