quarto-dev / quarto-dev/quarto
`Run Cell` in VScode starts spawning multiple `kioslave5` processes which consume all resources and crash
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
Steps to reproduce:
- Install the latest versions of vscode and extensions for python, jupyter, and quarto.
- Create a .qmd document with python chunks.
- Create a new jupyter interactive window.
- Execute chunks in the .qmd document through the button above the cell which says "Run Cell".
Problem description: things work as expected (input is sent to the interactive window), BUT shortly after, it starts spawning multiple kioslave5 processes in parallel, which consume all of the available CPU and make the vscode application unresponsive. Killing these processes manually doesn't appear to have any side effects. If not manually killed, these processes keep running even after the code process is killed.
The processes appear to be launched with the following command:
<kioslave5 binary> <path/to/kio_trash.so> trash local:/run/user/1000/kioclient<hash>.1.kioworker.socker`
Setup: Debian Trixie (testing), vscode 1.95.0, Quarto 1.6.32, running KDE 5.27.11 which is what provides those kioslave5 processes. Issue wasn't happening with previous versions of vscode, but I'm not sure if what broke it was today's vscode update or some other system update.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Start by reproducing the issue with a .qmd document and Python chunks in a Jupyter interactive window on Debian Trixie, then trace when the Run Cell action launches kioslave5. Done means repeated cell execution no longer spawns runaway processes and the processes stop when VS Code exits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter, linux, python, vscode
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100