[Bug]: Hanging, CPU spikes, segfaults

### I have done the following

- [x] I have searched the existing issues
- [x] If possible, I've reproduced the issue using the 'main' branch of this project

### Steps to reproduce

Any type of usage now leads eventually to Virtualization Server consuming 200-400% CPU, and stuck containers. Simply start some containers and use them for a few days.

### Current behavior

On recent builds the Virtualization Server tends to end up consuming massive CPU and the system eventually becomes unresponsive. Containers often run normally at first (although issues with the builder can make it difficult to create an image in the first place -- include seg faults during builds). The containers seem to run fine for a few hours to days before exploding in resource usage.

### Expected behavior

Idle containers should quietly consume zero resources.

### Environment

```markdown
- OS: 15.7.2 (24G325)
- Xcode: Version 26.1.1 (17B100)
- Container: 0.6.0 (build: release, commit: a23bcf0)
```

### Relevant log output

```shell
N/A
```

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Start by reproducing the long-running container workload described in the issue on macOS 15.7.2 with Container 0.6.0, watching for CPU spikes, stuck containers, builder failures, and segfaults. Collect relevant logs instead of the current N/A output, then identify a repeatable failure and verify that idle containers remain responsive without sustained CPU usage.

Written by the indexing model from the issue text.