N
Nuxt3mo ago
DoHn

How to debug Node memory allocation errors?

Hi! Recently my Nuxt app has started acting up a bit and during development I see these errors that completely crash the dev server:
✔ Nuxt Nitro server built in 804 ms nitro 5:36:47 PM
node(39651,0x17207b000) malloc: *** error for object 0x118b212f8: pointer being freed was not allocated
node(39651,0x17207b000) malloc: *** set a breakpoint in malloc_error_break to debug
✔ Nuxt Nitro server built in 804 ms nitro 5:36:47 PM
node(39651,0x17207b000) malloc: *** error for object 0x118b212f8: pointer being freed was not allocated
node(39651,0x17207b000) malloc: *** set a breakpoint in malloc_error_break to debug
Is there a flag or something I can use to find the culprit module?
3 Replies
Chad Fraser
Chad Fraser3mo ago
I have been getting this recently as well. They started about 5 days ago.
DoHn
DoHn3mo ago
oh ok, that's good to know. i guess it's the 3.11 update then?
DoHn
DoHn3mo ago
this looks like the related issue: https://github.com/nuxt/nuxt/issues/25115 closing this since issues are being opened about it
GitHub
Nuxi crashes on changes - pointer being freed was not allocated · I...
Environment Operating System: Darwin Node Version: v18.17.1 Nuxt Version: 3.6.5 Nitro Version: 2.5.2 Package Manager: yarn@1.22.21 Builder: vite User Config: ssr, hooks, css, serverHandlers, runtim...