Nuxt dev server hangs when using `findResultsState` with children routes

Bug 🐞

I have an odd issue when using Nuxt, SSR, and vue-instantsearch. Following this guide, I’ve made a stripped down demo repo of the bug in question (I’ve confirmed that the issue is happening with a fresh git pull, yarn and yarn dev of that repo).

It simply seems that some combination of using this.instantsearch.findResultsState in serverPrefetch and having a <router-view /> or <NuxtChild /> in the same component causes the dev server to eat a bunch of memory and eventually crash. Sometimes an event emitter error is printed to the dev server console. Aside from that, not much to go on.

[eugjlee]

Hello @Haroenv,

With Nuxt 2, I was also having memory leak issues. Using Siege, I was doing user simulation of 40 request in 30 seconds, and each time memory was increasing.

However, #1115 did fix the issue.
After building the library with #1115 , I was getting a constant 70mb usage which was not increasing in memory even after 120 request in 60 seconds.

#1117 did not fix the “TypeError: Cannot set property $nuxt of [object Object] which has only a getter” on my side. What I did to fix this was change a boolean on line 115 in createServerRootMixin, from true to false.

const isWritable = descriptor ? descriptor.writable || descriptor.set : false;

In Nuxt 2, descriptor is undefined, so I just made sure “isWritable” is set to false.

[podlebar]

@Haroenv i tried it and it does not solve the issue.