Misplaced .cursor folder caused editor to consume over 50GB of RAM

A developer discovered that the Cursor code editor was consuming over 50GB of memory on their Mac while working on a Next.js project. Initial debugging pointed toward the app itself, with checks for React render loops, memory leaks, and Next.js cache issues all proving fruitless. The root cause turned out to be a .cursor configuration folder nested inside a subdirectory instead of sitting at the project root. Moving the folder back to the correct location and fully restarting Cursor immediately resolved the excessive memory usage. The incident highlights the importance of checking hidden, tool-specific directories in a project when diagnosing unexpected editor or system performance issues.