Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Panic occurred at runtime. #5352

Closed
knames opened this issue Jan 16, 2024 · 6 comments
Closed

Panic occurred at runtime. #5352

knames opened this issue Jan 16, 2024 · 6 comments
Labels
bug Something isn't working pending triage The issue/PR is currently untouched.

Comments

@knames
Copy link

knames commented Jan 16, 2024

System Info

System:
OS: Windows 10 10.0.19045
CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12800H
Memory: 42.67 GB / 63.68 GB
Binaries:
Node: 18.16.1 - C:\Program Files\nodejs\node.EXE
npm: 9.5.1 - C:\Program Files\nodejs\npm.CMD
pnpm: 8.14.1 - ~\AppData\Roaming\npm\pnpm.CMD
Browsers:
Chrome: 120.0.6099.224
Edge: Spartan (44.19041.1266.0), Chromium (120.0.2210.133)
Internet Explorer: 11.0.19041.1566
npmPackages:
@rspack/cli: ^0.5.1 => 0.5.1
@rspack/core: ^0.5.1 => 0.5.1
@rspack/plugin-react-refresh: ^0.5.1 => 0.5.1

Details

When running a simple template project using rspack, I get the below issues. It's only on a windows machine, my mac works perfectly fine.

● ━━━━━━━━━━━━━━━━━━━━━━━━━ (11%) building scheduler
Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues
Message: internal error: entered unreachable code
Location: C:\Users\Administrator.cargo\registry\src\index.crates.io-6f17d22bba15001f\oxc_resolver-1.2.0\src\path.rs:69

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1: napi_register_module_v1
at
2: napi_register_module_v1
at
3: napi_register_module_v1
at
4: napi_register_module_v1
at
5: napi_register_module_v1
at
6: napi_register_module_v1
at
7: napi_register_module_v1
at
8: napi_register_module_v1
at
9: napi_register_module_v1
at
10: napi_register_module_v1
at
11: napi_register_module_v1
at
12: napi_register_module_v1
at
13: BaseThreadInitThunk
at
14: RtlUserThreadStart
at
 ELIFECYCLE  Command failed with exit code 3221226505.
\

Reproduce link

No response

Reproduce Steps

I'll have to make a simpler project without a bunch of internal company libraries. Will be back with a link for that..

@knames knames added bug Something isn't working pending triage The issue/PR is currently untouched. labels Jan 16, 2024
@knames knames changed the title Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues Panic occurred at runtime. Jan 16, 2024
@knames knames closed this as completed Jan 17, 2024
@pushkargupta9807
Copy link

pushkargupta9807 commented Feb 3, 2024

I am running into a similar issue with the 0.5.2. Works fine on Mac OS but runs into the Panic with windows.

#5592
@knames how did you get around this issue on windows?

@knames
Copy link
Author

knames commented Feb 3, 2024

I am running into a similar issue with the 0.5.2. Works fine on Mac OS but runs into the Panic with windows.

#5592 @knames how did you get around this issue on windows?

Might be hitting the limit on windows path length (256 characters unless you enable long paths), especially when using pnpm (crazy long nesting, they have a ticket to change it to hashes after 30 chars but who knows when that’s out).

Try getting as close to c:/ as possible, don’t use long names for folders. That’s what it was for my coworkers at least.

@pushkargupta9807
Copy link

well I tried by enabling the long paths in the registry - still running into that same panic. And I am using yarn.

@hardfist
Copy link
Contributor

hardfist commented Feb 4, 2024

well I tried by enabling the long paths in the registry - still running into that same panic. And I am using yarn.

what is your rspack version and try set chunkIds to deterministic

@pushkargupta9807
Copy link

well I tried by enabling the long paths in the registry - still running into that same panic. And I am using yarn.

what is your rspack version and try set chunkIds to deterministic

I am on rspack v 0.5.3 and I tried setting the chunkIds to "deterministic", but ran into the same error below:

Message: internal error: entered unreachable code
Location: C:\Users\Administrator.cargo\registry\src\index.crates.io-6f17d22bba15001f\oxc_resolver-1.2.2\src\path.rs:69

@dxhsmwqcwelllee
Copy link

Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues
Message: Module(/Users/doorgod/Desktop/www/AbcPc/node_modules/sax/lib/sax.js) should be added before using
Location: crates/rspack_core/src/chunk_graph/chunk_graph_module.rs:75

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.

Accidental phenomena, why?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working pending triage The issue/PR is currently untouched.
Projects
None yet
Development

No branches or pull requests

4 participants