-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
Illegal instruction #58050
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
Comments
after running const RedisStore = require('connect-redis').default;
_client = (CacheClient != null ? new RedisStore({
client: CacheClient,
prefix: "brS_",
}) : (() => {
console.error("[Cache]: connection to Redis Server is not handled!");
return undefined;
})()), |
cc @nodejs/libuv it seems this is a libuv bug |
hey @Zorono, could you please create a small repro that doesn't rely on external dependencies, or at least provide one if you're unable to reproduce the issue without dependencies? |
Removed the libuv label for the reason @pmarchini mentions. |
From the stack trace it looks like some code in the user land is sending process.kill(SIGILL) to itself or its child. You might want to search in your code and your dependencies to find out which part of your code base is doing that, it could be that some code you have is catching whatever error that gets thrown and sending SIGILL, but this doesn't look like an actionable issue of Node.js core since the signal is raised by the user. |
it seems like you're correct. Thanks for pointing out this mistake |
Version
v20.19.1
Platform
Subsystem
No response
What steps will reproduce the bug?
i can't make sure where is the problem...
How often does it reproduce? Is there a required condition?
Every execution of node
What is the expected behavior? Why is that the expected behavior?
Run my ExpressJS server
What do you see instead?
Node process crashes once i try to load my ExpressJS Server
Additional information
All of my recent commits to the Project were in client side and the last commit was 5 months ago which was running perfectly before the release of this node version... and I can't find which one of my old commits is the cause of this crash
The text was updated successfully, but these errors were encountered: