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

Ouverte
#1,801 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
18/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
ios, macos, typescript
Domaine
devtools

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
705
Forks
40
Merge moyen
12 h 9 min
PR mergées (30 j)
376

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de callstackincubator/simlock

Toutes les issues de callstackincubator/simlock

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.