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

オープン
#1,801 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
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分
マージ済み PR(30日)
376

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

callstackincubator/simlock のほかの issue

callstackincubator/simlock の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。