memory leak with `useHead`

Environment

Netlify lambda

Reproduction

https://github.com/Rigo-m/bridge-nitro-generate-sourcemaps -> Bridge https://github.com/atoms-studio/netlify-odb-cache -> Nuxt3

1. create a netlify site for each
2. take a peek at function/server log
3. hit some random slugs to generate pages via on demand builder (e.g.: your-netlify-handle.netlify.app/1, your-netlify-hande.netlify.app/2

Describe the bug

Nuxt3 is better than bridge, but it seems like there is some sort of memory leak. Lambda’s memory keeps raising every time you invoke a new web page (already invoked ones are cached via on demand builders). In a big website we’ve made with bridge, lambda crashes every once in a while because of memory impairments.

Here’s a log example: https://pastebin.com/bsY1bpwf

Additional context

No response

Logs

https://pastebin.com/bsY1bpwf

[Jackliu007888]

我也遇到内存泄露 在alinode排查时发现 allHeadObjs 这个可疑点

https://github.com/vueuse/head/issues/36 这个好像也是相似的错误

[Jackliu007888]

@Rigo-m @danielroe I have a memory leak problem, through alinode monitoring, get the HeapSnapshot file, analysis found that “Set” object and “ReactiveEffect” object can be suspicious.

Heapsnapshot analysis shows that there are many ”meta2“

Here does not need to use ref ?