vibehacker
Discuss
Riley
2 months ago

cursor + xcode both indexing and my mbp fans won the demo

had a stakeholder call yesterday. flutter ios build already chewing memory, then i let the cursor agent "just fix the null check" in the payment sheet.

activity monitor jumped past 18GB. xcode indexing froze. fans sounded like a leaf blower. shared screen went black for like 8 seconds.

agent finished the null check. also rewrote my Riverpod provider "for clarity". wrong. demo recovered after i force-quit cursor.

anyone else kill the agent before opening a simulator, or am i the only one still learning this the hard way?

5 comments

Join the discussion

Log in to comment.

  • Soren Wong

    same class of failure on my M2 Max. cursor agent + ollama qwen2.5:14b in the background hit unified memory hard enough that Xcode's SourceKit just... stopped answering.

    i started closing ollama before any flutter/ios work. agent alone is still greedy but at least the fans stay under control. the "for clarity" rewrite is the part that actually burns me — green compile, wrong state graph.

    • Pixel

      tried keeping cursor open through a playwright + vite demo last week and chrome froze instead. not flutter but same vibe.

      do you actually quit the agent or just pause it? i keep hitting "accept all" when the fan noise starts and then i own the bad diff. curious if anyone has a hard rule like "no agent while xcode indexing > 0".

      • Jade

        i pause it. quitting fully is cleaner but i forget and reopen mid-call.

        hard rule that actually stuck for me: if Xcode's indexing bar is visible, agent stays paused. no exceptions. learned after it "fixed" a SwiftUI binding while SourceKit was half-rebuilt and the preview showed stale state for 10 minutes.

    • Drew Moore

      yeah i kill ollama before any xcode work now. pkill -f ollama is in a shell alias next to my sim boot script.

      agent alone on a 14b local model is still enough to stall SourceKit on my M2. cursor's indexer + apple's indexer fighting over the same SSD is undefeated.

  • Carlos Reed

    happened to me on an M3 Pro last month — not even flutter, just cursor agent + docker desktop + a chrome tab with the staging app.

    activity monitor showed Cursor Helper (Renderer) at 9GB before the screen share died. i now quit docker before any client call. feels ridiculous but the fans stay quiet.

    the "for clarity" rewrite is the real landmine. green build, wrong mental model, and you're explaining it live.

More like this

View all