Orphan iOS devices stay on disk after a failed shutdown; `cleanup` doesn't see them

未关闭
#1,801 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
18/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
ios, macos, typescript
领域
devtools

调研方向

The failure sits in the shutdown and delete path: the device.purge-failed and device.quarantined events come from the daemon's shutdown step, and the orphan detection is the doctor orphan-device check. Read the lease-end shutdown code, the quarantine retry logic, and how cleanup selects devices, then compare them with the clone/create timeout change referenced in #1563. Done means a quarantined device gets a final forced delete, cleanup removes orphans, and a rejected request deletes its simulator, with tests for each path.

由索引模型根据 Issue 内容生成。

描述

bug:new
What happened

On a 16 GB Mac under memory pressure, deleting a simulator at lease end runs simctl shutdown with a 30 s timeout. The daemon log shows it timing out, then the device is quarantined and the reclaim retries fail:

device.purge-failed  DriverCrashError: simctl shutdown <udid> timed out after 30000ms
device.quarantined   kind: shutdown-failed
quarantine reclaim retry failed (attempts 3)

Some of those simulators stay in ~/.simlock/devices/ios with no row in simlock list. I had three (1.2 to 1.5 GB each), left on 0.7.0. After upgrading to 0.8.0 and restarting the daemon they were still there, and only doctor saw them:

$ simlock --version
0.8.0
$ simlock list            # only the one live lease
$ simlock cleanup --dry-run
[]
$ simlock doctor
{"findings":[{"kind":"orphan-device", ... "platform":"ios"}, (x3) ...]}

A handful of these push the disk under the 10 GB pressure line. Two orphans in an earlier batch came from provisions whose requests were then rejected with unresolvable-spec, so a rejected request may also leave its new simulator behind.

This looks like the shutdown/delete side of #1546. #1563 bounded clone/create and deletes a late copy, but the shutdown at lease end still has the fixed 30 s limit, and a daemon restart does not reconcile the orphans.

What I expected
  • A quarantined device whose retries are used up gets a last forced simctl delete.
  • cleanup (or a periodic doctor reconcile) removes orphan-device findings.
  • A rejected request deletes the simulator it created.
How to reproduce

The shutdown timeout only happened under memory pressure (swap about 2.5 GB, pressure "warn"), so that part is intermittent. Once orphans exist, the list / cleanup / doctor check above shows them every time.

Environment

simlock 0.8.0 (orphans created on 0.7.0), macOS 27, iOS 27.2 runtime.

Workaround

simlock doctor --purge-orphans --yes removed all three on 0.8.0 without a daemon restart. A restart alone does not clear them.

Suggested fix

Give the shutdown at lease end the same kind of setting #1563 added for clone/create, and run the orphan reconcile from cleanup or on a timer.

主要语言
TypeScript
星标
705
派生
40
平均合并
12 小时 9 分钟
30 天内合并 PR
376

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

callstackincubator/simlock 的其他 Issue

查看 callstackincubator/simlock 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。