Issue setting up the project in local
After following the official documentation, when running
npx nx start twenty-server, I am getting the error for which I have attached the screenshot.
Also, when running npx nx start twenty-front, I am seeing the error of unable to reach backend. I have also done In packages/twenty-front/.env uncomment VITE_DISABLE_TYPESCRIPT_CHECKER=true and VITE_DISABLE_ESLINT_CHECKER=true.
31 Replies
Hello @Kash_04 what are your hardware specifications ?
16 GB RAM, 512 GB SSD, HP HP Pavilion Laptop 15-eg2xxx, Intel i7 12th gen
Should be largely enough to run Twenty
Are you encountering the issue on main ?
Yes. I am encountering it on main. Have been reading the chats and documentation but whatever was suggested, I tried and still it isn't working
Are you on windows or a unix system ?
Are you using a vm by any chance ?
I am on unix system and not using any vm. Also, the postgres and redis setup has been done on my local machine and not any docker containers
Would need more information on what you've done in order to achieve to this
Have you correclty installed all deps ?
Followed the guidelines as given in the docs.
Can't guess what's not working on your local setup
so what additional info can I provide you with?
From your screenshot its' not possible to determine what
twenty-front start sub command leaded to the JS OOM
Please share logs of:
these are my yarn logs
npx nx build twenty-front
There are many file names along with their sizes. I haven't included all those screenshots.
npx nx start twenty-front logs
@prastoin I have shared the logs.
Sorry I was sleeping, during night
Looking at you screenshots everything looks fine ✅
Is the wront ooming after few minutes ? because here it looks fine
Sorry, wasn't aware of the time difference. Will keep that in mind from now on.
While starting the frontend, I am getting the error of unable to connect with backend after a few minutes.
That's all right no worries
While starting the frontend, I am getting the error of unable to connect with backend after a few minutes.This means that only your backend is not working, I assume this the one having the oom issues ?
yeah
Could you please try building your backend on its own first using
So we can determine at what step it gets crazy
There is no error while building the backend.
The server shouldn't be greedy in ram
Does it keep OOMing even if you don't hit it ?
Sorry for replying late. But after
npx nx start twenty-server, without even hitting it, after a few minutes of running the command, I get this error.
Could you please review your cpu memory on live while bootstraping the app to see if for some reason the server just explodes in cpu usage ?
@Prastoin could you please guide me on how do i check this?
facing the same issue on wsl2, allocated 12 gb of RAM
Hello guys unfortunately it's going to be quite though to debug this remotely on your pcs, one thing we could still to do on our side is try debugging the local env on a wsl instances as you guys do
What you can do is track/record your task manager activity usage per program while building or trying to start the app trying to determine what's making the oom error exactly
I am getting the same error on wls I have 32GB Memory
@charles seems like we have an oom issue for contributors working on wsl might wanna create an issue
Hi, I had the same issue before and I fixed it with
export NODE_OPTIONS=--max_old_space_size=4096