Server Memory leaks, high CPU usage - appConfig

[burda-osowiecki]

Environment

• Operating System: Darwin
• Node Version: v18.15.0
• Nuxt Version: 3.2.3
• Nitro Version: 2.3.2
• Package Manager: npm@9.6.2
• Builder: vite
• User Config: -
• Runtime Modules: -
• Build Modules: -

Reproduction

I cannot reproduce it in small scale and ofc also cannot share our project code...
I hope someone other will have similar problem and be able to reproduce in from scratch.

Describe the bug

Additional context

We disabled all plugins and unnecessary third party libraries.
I was also trying the solution from this issue:
unjs/destr#9
I passed a parseResponse option to useFetch but it didn't change anything.

No response

Logs

No response

[danielroe]

Would you provide a reproduction? 🙏

You don't need to share exactly your code, but sharing the kind of code you are running is a helpful start.

cc: @pi0

[burda-osowiecki]

@danielroe, @pi0
Looks like the problem causes appConfig.
I moved the appConfig (which is constant object in our case, set in nuxt.config.ts) to key in runtimeConfig, then created a composable to return this object from runtimeConfig and replaced all usage of useAppConfig.
Thats the results. It also affects the CPU usage.
I'll try to create a reproduction.

[burda-osowiecki]

@danielroe finally I prepared the reproduction.
https://github.com/burda-osowiecki/nuxt-memory-leak

npm run build
npm run start:debug
gtimeout 10 siege -c 10 http://localhost:3000

10 requests its enough to see how much it leaks, looks like it depends on how many data is in store's state.

[burda-osowiecki]

@danielroe
App with reproduction - It resolves the problem
Our production app - It still leaks, so there must be something else :(

I'll try to create one more reproduction :/

[hoersamu]

We have the exact same issue. I'll try the useAppConfig workaround but it's causing a massive headache for us too.

[burda-osowiecki]

@danielroe I'm trying to update Nuxt to 3.4.2 to check the leaks on latest version but I encountered new bug.
Luckily I made a reproduction #20473

[burda-osowiecki]

@danielroe I've great news.
Looks like #20510 also resolves memory leaks!
(Tested on Nuxt 3.4.2, updated others dependecies like pinia to the latest and applied fix with callAsync)

#20340 is not necessary.

Please keep the thread open until we test it on production after uprading to 3.4.3 :)
Release of 3.4.3 is planned for Friday 28.04 right?

[danielroe]

Fantastic - and you're definitely on top of testing this!

[burda-osowiecki]

The problem is gone on 3.4.3!

Now the only one we have is: #20683