-
Notifications
You must be signed in to change notification settings - Fork 286
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
Get the js stack trace of a running nodejs process #4039
Comments
@ericzhucode you can fire a |
Yes I know that and actually if you use vscode to debug nodejs via pid then vscode will automatially send |
Same question on my end, would love to know if this is possible @MoLow! Thanks for all your help. |
Maybe this one can help here https://blog.apify.com/how-to-debug-an-infinite-loop-in-node-js-production-code/ |
@ericzhucode Were you able to try out the suggestions above? |
It seems there has been no activity on this issue for a while, and it is being closed in 30 days. If you believe this issue should remain open, please leave a comment. |
It seems there has been no activity on this issue for a while, and it is being closed. If you believe this issue should remain open, please leave a comment. |
Details
Background: If there's an infinite loop in js script, it would be hard to find it. Currently if we found a nodejs process stucks, we would use nodejs debug feature to attach to that process and then pause it, in that way we can find the code of the infinite loop like
I'm wondering if there's any params or tools of nodejs to help us output all stack trace of running nodejs process to a log file, so that we can find the infinite loop?
Or is there any other better ways to find the exact code of an infinite loop?
Thank you for your help!
Node.js version
All versions
Example code
No response
Operating system
All systems
Scope
code
Module and version
Not applicable.
The text was updated successfully, but these errors were encountered: