I'm developing in WSL2 with 16GB of RAM available to the WSL VM.
I decided to try and upgrade a Next.js 15 repository to v16, but whereas previously running next dev --turbo pushed the WSL VM up to about 6GB (via Windows Task Manager's Memory page, so not necessary all that accurate, but anyway...), doing the same with v16.2.4 hits the 16GB, then starts maxing transfers on the SSD (presumably to swap).

Loading even the home page becomes impossible (WSL crashes out before it loads).
Reverting to 15 and it works fine.

What should I be looking at as the cause of the issues? (I suspect I have not migrated something critical, or I overenthusiastically cached somethings, but the outcome here is extreme).

Setting experimental.preloadEntriesOnStart to false didn't have an observable change (beyond it being printed to the console at start).