-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Crash when taking a heap snapshot #38985
Comments
Is it possible to provide some code that can be run to reproduce this? |
This is commercial code so unfortunately I cannot provide it. I don't currently have the time to work on a minimal reproducer. It pretty reliably crashes when taking a snapshot while the process is active. Is there any other data I can provide beyond the code and backtrace? |
Unfortunately, I'm afraid that we can't help you debug much if we can't reproduce it ourselves 😞 |
Also segfaults when running the code one-shot when heap profiling "Allocation instrumentation on timeline" and "Record stack traces of allocations (extra performance overhead)" checked. This crashes 100% of the time several minutes into the run with:
|
Using
|
(The crash in |
I seem to have managed to reproduce the same heap snapshot crash, with my own debug build from commit ce4d224 on the v14.x branch (EDIT: I was unable to reproduce this crash from my build at commit 1543497 on the v16.x branch; it appears to be fixed there). This appears to have provided me with some more details from the core file, including a few additional stack frames on top of
|
same issue with 14.17.3-2.module+el8.4.0+639+18660d0d (rocky 8) |
Your issues may be similar to the one I hit: #41539 Btw @jaysoffian, thank you so much for this small comment:
It is what helped me reproduce the problem in a reliable manner, ultimately leading to the small and self-contained repro code linked in the issue above. |
What steps will reproduce the bug?
I have a node process that crashes fairly consistently when taking a heap snapshot via Chrome dev tools. Here's a stack trace captured by lldb:
(Process started using
lldb -- node --inspect index.js
.)How often does it reproduce? Is there a required condition?
This process runs tasks periodically via npm package
cron
. The crash seems to be more likely to occur while the node process is actively running a task.What is the expected behavior?
Not to crash.
What do you see instead?
Crash.
Additional information
Roughly, this code periodically uses the
got
package to query data from a couple different APIs, then insert the data into MySQL using themysql2
package. As mentioned above, the crash is more likely to occur while the process is actively querying data and inserting it into MySQL. Running it underlldb
seems to further increase the likelihood of the crash occuring.The Chrome version is 91.0.4472.77 with built-in dev tools.
Node installed via
nvm 0.38.0
.The text was updated successfully, but these errors were encountered: