Pablo Dávila

Just adding to this that I'm having the same problem.

I found that limiting WSL's RAM usage in .wslconfig helps. I'm assuming the issue isn't really solved but it can avoid RAM usage from ballooning. I have it limited to...

Updating on my previous comment, at some point the .wslconfig file is essentially ignored as VS Code simply takes all the RAM it wants. My guess is that this issue...

Just to confirm that I'm getting the same error with my 404 and 500 pages, using the edge-runtime option and Next 13.

@christophberinger I'm getting the same issue. Did you happen to find a fix?

Sorry, I'm no longer using the library. But as far as I can remember, I couldn't find a solution for this. @yakovlevkll