Uisng @swc/jest crashes with thread '<unnamed>' panicked at 'failed to invoke plugin

[AbhiPrasad]

Describe the bug

@swc/jest causes jest to crash in CI when using the jest_workaround plugin.

GH action run: https://github.com/getsentry/sentry-javascript/actions/runs/4437301786/jobs/7787193218

PR w/ crash: getsentry/sentry-javascript#7484

SWC versions:

    "@swc/core": "1.3.40",
    "@swc/jest": "0.2.24",

jest_workaround versions:

  "jest_workaround": "0.1.16",

Input code

No response

Config

No response

Playground link

No response

Expected behavior

Not crash when running jest

Actual behavior

> @sentry/core:test

$ jest
thread '<unnamed>' panicked at 'failed to invoke plugin: failed to invoke plugin on 'Some("/home/runner/work/sentry-javascript/sentry-javascript/packages/core/test/lib/base.test.ts")'

Caused by:
    0: RuntimeError: out of bounds memory access
    1: heap_get_oob', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/swc-0.255.3/src/plugin.rs:228:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Segmentation fault (core dumped)
error Command failed with exit code 139.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Version

1.3.40

Additional context

No response

[kdy1]

This is not a bug of swc/core

[AbhiPrasad]

Hey @kdy1 - is this a problem with jest_workaround? Or with jest? What do I need to do to investigate this further?

[kdy1]

I think jest_workaround is the cause.
See https://swc.rs/docs/plugin/selecting-swc-core

[AbhiPrasad]

Awesome, opened a bug report (magic-akari/swc_mut_cjs_exports#30) with jest_workaround, thank you!

[magic-akari]

I think jest_workaround is the cause.
See https://swc.rs/docs/plugin/selecting-swc-core

I have updated the swc_core dependencies to the latest version.
The issue did not get resolved, even though it worked fine on my unit tests.
Besides an incompatible version of swc_core, I cannot find other reasons for the out of bounds memory access.
@kdy1 Do you have any leads on this?

[kdy1]

I think #6807 can be relevant.
What's the version of rustc?

[kdy1]

Oh it's pinned. Hmm

[AbhiPrasad]

The branch with the tests failing is on https://github.com/getsentry/sentry-javascript/tree/abhi-build-swc-jest. Please let me know if you need me to debug/run anything to test stuff out.

[kdy1]

@AbhiPrasad Can you run CI again with RUST_BACKTRACE=1?

[kdy1]

I ran in locally with @swc/core@1.3.41 with jest_workaround@0.69 but it worked.
I'm using Apple M1 Max chip

[AbhiPrasad]

Works for me locally as well - going to hard-pin the deps you mentioned and run in CI.

Unfortunately downloading node is having problems, so CI might flake a couple times while we wait.

[AbhiPrasad]

Weird, hard pinning is now working fine for me - so maybe this was something on my side not sure.

https://github.com/getsentry/sentry-javascript/actions/runs/4447652660/jobs/7809706494?pr=7504

Now just getting errors around jest stuff in CI, but that's probably because jest_workaround is playing weird with old jest version. Will close this for now then, thanks for taking a look!

[swc-bot]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.