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

High Memory issue at version 2.6.0 #772

Closed
ambika93 opened this issue Jan 9, 2019 · 8 comments
Closed

High Memory issue at version 2.6.0 #772

ambika93 opened this issue Jan 9, 2019 · 8 comments

Comments

@ambika93
Copy link

ambika93 commented Jan 9, 2019

Team,
I'm using 2.0.6 version. After activating apm on service, memory increases gradually. At start of service memory is around 2 GB, which increases to 8 GB after 3 days and so on.

I'm using all default configurations.
Node dependency as below:
"aerospike": "3.0.2",
"async": "^2.6.0",
"bitset.js": "~4.0.1",
"body-parser": "^1.14.1",
"commander": "^2.9.0",
"ejs": "^2.3.4",
"express": "~4.9.6",
"kafka-node": "^2.6.1",
"lodash": "~3.10.1",
"moment": "~2.10.6",
"morgan": "~1.3.2",
"mysql": "^2.10.2",
"newrelic": "~1.29.0",
"node-uuid": "^1.4.7",
"nodemailer": "0.7.1",
"on-finished": "~2.3.0",
"q": "^1.4.1",
"redis": "^2.4.2",
"request": "^2.69.0"
I'm using new relic but it is disabled currently.

@watson
Copy link
Member

watson commented Jan 9, 2019

When you say that new relic is disabled, in what way do you mean? Are you still requiring the newrelic module or is it just in your dependencies but not required?

@ambika93
Copy link
Author

ambika93 commented Jan 9, 2019

It's just a dependency and not required.

@watson
Copy link
Member

watson commented Jan 9, 2019

Thanks 👍

Are you able to reproduce the problem in a small test-application that you can share with us? It would help us a lot in debugging the problem.

@ambika93
Copy link
Author

ambika93 commented Jan 10, 2019

@watson I'll try to reproduce issue on small test application. For now, I'm sharing memory graph. Normally it remains around 2 GB.
memoryincrease

@ambika93
Copy link
Author

@watson I've taken heapdump at my service. And i found issue with async hooks. I'm using node 8.12.0. I disabled asyncHooks and testing. I will update same.

@watson
Copy link
Member

watson commented Jan 15, 2019

Oh, interesting. Thanks for debugging this and sharing your progress.

I'd love to hear more about exactly what's causing it or if you can share a reproducible test-case. There were a fix in v8.13.0 for an async hooks bug that I think could cause memory leaks in some cases - so it would also be interesting to see if the issue went away if you upgraded.

@watson
Copy link
Member

watson commented Mar 12, 2019

@ambika93 Did you get a chance to upgrade to a newer version of Node.js to see if the issue went away?

@watson
Copy link
Member

watson commented Mar 19, 2019

Closing for now due to lack of activity. Feel free to leave a comment if you want this to be reopened.

@watson watson closed this as completed Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants