https://nuxtjs.org/guide/installation
install app using CLI
cd into directory
run npm install
run npm run dev
at this point the dev sever should be running
open browser tab (i use chrome) and launch app http://localhost:3000
verify that you can see app and its working as intended
launch app in several tabs in quick succession
On a mac using Chrome, you can achieve this by hitting command + l followed by command + enter
Able to access several instances of the app concurrently without faults
opening 5-10+ tabs all requesting a new instance of the app will cause the app to fail and not function
For a while we were running into heap memory problems so we increased our heap to 8gb and then we ran into

we've been using the methods listed in the reproduction steps to simulate several users hitting the system at once to stress test it, but we've never been able to do so. We thought it might be a 3rd party library causing the situation so i created blank cli projects for starters and thats where I found out that nuxt out of the box cant handle this situation very well. Some basic info on what my app is actually using: nuxt 1.4.2, node: 8.11.3, nuxtjs/axios module: 5.3.1, js-cookie: 2.2.0, jwt-decode: 2.2.0, vuetify: 1.1.9
Does this happen in production mode (npm run build && npm run start) as well? :thinking:
Does not appear so 馃
Wouldn't see it as a bug then :relaxed:
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Most helpful comment
Does this happen in production mode (
npm run build && npm run start) as well? :thinking: