行业81°

微软宕机事故内幕:4个月前的"潜伏bug",人工代码惹祸

精选理由

一线负责人透露细节:4个月前一次人工提交埋下潜伏bug,机器被打满后失联,靠一个开发者翻dump才找到根因,AI工具只是辅助。等微软公开复盘出来,做基础设施的都该看看。

Gergely Orosz 与一位参与事故处置的微软团队负责人通话,还原了这次宕机的技术细节。事故根源是一个约4个月前提交进 Windows 构建的"潜伏bug",它延迟触发,导致机器资源饱和后失联。

正文

该代码由人工编写和提交,与 AI 无关。事故期间还叠加了一连串 unlucky 事件,最终是一名开发者在排查中看到一处 dump 文件与见过的错误模式吻合,才定位到根因,AI 诊断工具在恢复过程中起了辅助作用。

微软计划在全球完成修补后发布公开的详细事后复盘报告。这类延迟激活的提交在大型代码库中极难排查,事后复盘对工程团队会有参考价值。

原文 · Gergely Orosz

Got off a call with the an MS team lead who was on the bridge for this incident on what exactly happened in the outage:

1. This was a "latent bug" - a commit going in ~4 months ago to a Windows build, that only activated much later. Super hard to spot

2. Zero AI, this code was human written + committed

3. Machines got saturated and unreachable at a result

4. So many other things went wrong during this outage: a series of unlucky events

5. It was a dev who found the root cause, poking around and seeing a dump that reminded them of an error seen here. AI diagnostic tools were used and helped progress with the outage

A detailed, public postmortem is on its way. MS wants to make sure they have everything patched globally before the postmortem. I'll add my two cents when it's out, and those details will be VERY educational

产业坐标与信源核验

本条情报归属 AITOP「行业」核心栏目,重点聚焦北美前沿实验室与硅谷科技巨头。在跨区域产业观察坐标中,该动态直接关联「AI 开发者工具链、Coding Agent 与工程化实践」研究主线,反映出当前技术演进与商业落地的最新风向。涉及核心实体与技术议题包括:Microsoft、Windows、故障复盘、SRE,读者可通过下方标签进入对应专题页查阅历史脉络与关联对比。

信源核验说明:本文原始线索采编自「Gergely Orosz」(@GergelyOrosz),经 AITOP 多维评分管线结构化提炼。