-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Memory Leak on AWS ECS #927
Comments
Would you see if you can reproduce with just nitro and, if so, open an issue on https://github.com/unjs/nitro instead? 🙏 |
I'm not using nitro in this project. Nitro is set false in bridge config. But i'm gonna try with nitro and vite. I hope i can make it. There's lots of error occurs when i set nitro and vite set true. |
Oh, if you're not using nitro then the memory leak will probably still reproduce if you enable it. What makes you think this is an issue with bridge? Does it reproduce outside AWS ECS? (I would recommend trying with |
Project runs into docker container in ecs. But i cannot reproduce in my local docker enviroment. This makes things quite interesting. When i watching memory usage in node inspect everything is normal. Garbage collector works fine in my local. I'm gonna try with |
probably |
There's no memory leak witn latest |
Environment
Darwin
v16.20.0
2.16.0-27717142.54e852f
0.4.24
[email protected]
webpack
srcDir
,alias
,server
,bridge
,sourcemap
,head
,css
,styleResources
,plugins
,buildModules
,gtm
,modules
,sitemap
,postcss
,tailwindcss
,typescript
,sentry
,buefy
,image
,axios
,proxy
,render
,i18n
,router
,build
,serverHandlers
,devServerHandlers
@nuxt/[email protected]
,@nuxtjs/[email protected]
,[email protected]
,@nuxtjs/[email protected]
,@nuxtjs/[email protected]
,[email protected]
,@nuxtjs/[email protected]
,[email protected]
,@pinia/[email protected]
,@nuxtjs/[email protected]
()
,@nuxtjs/[email protected]
,@nuxtjs/[email protected]
,@nuxtjs/[email protected]
,@nuxtjs/[email protected]
,@nuxtjs/[email protected]
,[email protected]
,@nuxt/[email protected]
Reproduction
I cannot reporduce because that's very huge project. I just wanna trace where memory leak happens.
Describe the bug
Here's the memory utilization on AWS ECS Monitoring section. The parts where the decrease occurs are when the container is restarted due to out of memory.
Additional context
And how can i trace where memory leaks come from? Any tips for tracing?
Logs
The text was updated successfully, but these errors were encountered: