## Description

Switching an Omarchy theme while btop is running can terminate btop with SIGABRT. The theme itself applies successfully, but the btop reload initiated by the theme command exposes a known upstream GPU-layout bug.

This has occurred twice on this machine with the same stack.

## Steps that trigger it

1. Launch btop through Omarchy.
2. Leave btop running with GPU detection enabled.
3. Switch to another Omarchy theme.
4. btop aborts during the theme-triggered configuration reload.

I have not deliberately generated an additional crash after identifying the mechanism.

## Confirmed timeline

For the 2026-08-27 incident:

```text
21:41:39.241  New theme files installed
21:41:39.452  "solitude" recorded as the current theme
21:41:39.632  systemd-coredump begins processing btop SIGABRT
```

The earlier 2026-08-25 incident also followed an Omarchy shell theme application by approximately 183 ms and produced identical btop offsets.

## Omarchy integration path

`omarchy-theme-set` includes `omarchy-restart-btop` among its post-theme commands.

`omarchy-restart-btop` currently performs:

```sh
pkill -SIGUSR2 btop
```

btop treats SIGUSR2 as a configuration hot reload. During that reload, btop’s runner reaches an out-of-range access to its GPU layout vector.

## Crash mechanism

The crashing program is Arch’s `btop 1.4.7-1`. Both recorded crashes resolve to:

```text
std::__glibcxx_assert_fail
std::vector<std::string>::operator[]
Gpu::draw(...)
Runner::_runner(...)
```

Instruction-level inspection identifies the vector as `Gpu::box`; the failed assertion is:

```text
__n < this->size()
```

The corresponding upstream access is:

```cpp
out += box[index];
```

Upstream report with the same mechanism:

https://github.com/aristocratos/btop/issues/860

The underlying bounds bug belongs to btop. This Omarchy report concerns the reproducible integration failure: a normal theme switch unconditionally invokes the reload path that exposes the current packaged btop bug.

## Expected behavior

Changing themes should recolor or safely refresh a running btop instance without terminating it.

## Actual behavior

The theme applies, but btop aborts and systemd-coredump records a core.

## System information

```text
Omarchy: 4.0.1-1
btop: 1.4.7-1, GPU_SUPPORT=true
Kernel: 7.1.9-arch1-2
Architecture: x86_64
CPU: Intel Core i7-14700F
GPU: NVIDIA GeForce RTX 4070 SUPER
Theme selected in latest incident: Solitude
```

Saved btop configuration:

```text
shown_boxes = "cpu mem net proc"
show_gpu_info = "Auto"
cpu_graph_lower = "Auto"
cpu_graph_upper = "Auto"
```

There was no OOM event, and no user data was lost.

## Suggested scope

Please consider an Omarchy-side guard or temporary safe-reload workaround for affected btop versions until upstream resolves the bounds bug. This report does not attribute the underlying invalid vector access to Omarchy.

Filed by GPT-5 via Codex.