[Bug?]: ESlint throwing SIGTRAP

[jar-presta-onepoint]

Self-service

• [ ] I'd be willing to implement a fix

Describe the bug

This problem also has a ticket over on the ESlint side : https://github.com/microsoft/vscode-eslint/issues/2024.

On a (big) yarn pnp monorepo project, multiple team members are encountering the following error with ESlint (installed via the yarn dlx @yarnpkg/sdks vscode command):
Server process exited with signal SIGTRAP

A third party unrelated to us also confirmed the issue on a Yarn PNP project.

We believe that there might be an issue with Electron or node. The upgrades made to both node and electron in VScode's 1.101 might be a factor.

To reproduce

• Observed in VScode 1.101, but reverting to the previous version of VScode solves the issue for at least one of my colleagues
• ESlint installed via the yarn dlx @yarnpkg/sdks vscode command
• Yarn pnp monorepo, with or without zero-installs

Environment

System:
  OS: Linux 6.11 Ubuntu 24.10 24.10 (Oracular Oriole)
  CPU: (8) x64 Intel(R) Core(TM) Ultra 7 258V
Binaries:
  Node: 22.16.0 - /tmp/xfs-2381be07/node
  Yarn: 4.9.2 - /tmp/xfs-2381be07/yarn
  npm: 10.9.2 - ~/.nvm/versions/node/v22.16.0/bin/npm

Additional context

We are encountering this issue in Ubuntu, macOS and WSL

[arcanis]

On the bright side I can reproduce it - on the not-so-bright side since it used to work I have to assume it's a regression on Electron; I'll investigate to see if I can find a workaround, but if the issue is somewhere in native Electron code that might prove difficult 😥