内存一周涨满一次，重启就好
内存一周涨满一次，靠每周三凌晨重启扛着，已经两个月了。
Copy the prompt, then pick a model. It plays the interviewer and asks you through it scene by scene instead of handing you the answer.
On a phone with the app installed, the system opens the app directly. Links cannot open external apps inside WeChat — open it in a browser first.
「重启就好」很容易让人直接归成「泄漏」，然后一头扎进「找哪个对象没释放」——而这一份的真相不在那个方向上。
内存一直涨至少是三种完全不同的东西，处理办法也完全不同。先分家，再往下走，顺序是固定的：堆内还是堆外 → 直方图 → 持有链。跳过前两步直接猜「是不是 ThreadLocal」，是这类问题上最常见的浪费。
现场里正好摆着两个教科书上的经典嫌疑人等你扑上去。
The move this one drills
Have you done this one?
Sign in to mark this one as practised — next time you come back you'll see when you did it.
Notes from people who did this one
How to use this
It gives you the scene (what the service is, the symptom, when it started, the blast radius) and then goes quiet. You ask questions, request metrics, logs, packet captures, propose hypotheses — it answers from a truth you cannot see.
**It is not allowed to volunteer where to look next.** If you don't ask, it doesn't say — even if you circle for ten minutes. That's deliberate: in real life nobody stands next to you saying "maybe check the flame graph". Troubleshooting *is* the skill of knowing what to ask.
How to start
- Pick one, open it, copy the prompt.
- Paste it into a brand-new conversation.
- It gives you the scene and stops — **now it's your turn to speak.**
Four commands you can call out at any time
给个方向give me a direction, not the answer (counted in the tally)公布真相reveal the truth and wrap up换一个start over with a different incident复盘wrap up now and print the review card
Three traps
- Don't read the truth at the end first — that ruins the whole thing.
- Don't start by guessing the cause. Establish the scope first (how much, which part, when it started); scope tells you whether this is a code problem or an environment problem.
- Every scene has planted false leads: an unrelated deploy at the same time, metrics that are effects rather than causes, the textbook suspect waiting for you. The wrap-up tells you how many questions you spent on each.
Start with the P99 one — its diagnostic chain is the cleanest. Then "only some machines", whose lesson is the most reusable of all. Save the intermittent timeout for later: its answer lives outside your own system. The report mismatch needs no systems knowledge at all.
Sign in to write a note.