Mac OS 9 Diagnostic Tools for Rogue Extension Leaks

During the Mac OS 9 era, the operating system lacked protected memory and preemptive multitasking, meaning a single rogue extension could continuously consume system heap memory until the computer froze or crashed. Identifying which extension (or "INIT") was responsible for memory leaks required specialized third-party and developer tools designed to inspect memory heaps, monitor process footprints, and automate extension conflicts. This guide outlines the key diagnostic utilities vintage Mac users and developers relied on to identify, isolate, and eliminate problematic extensions causing memory degradation.

Conflict Catcher

Developed by Casady & Greene, Conflict Catcher was the definitive industry standard for resolving extension-related instability. While not strictly a memory profiler, it directly addressed the primary cause of extension memory leaks: bad code interactions.

Conflict Catcher utilized an automated binary search method. Upon reboot, it would disable half of the installed extensions, test for the issue, and systematically narrow down the culprit through successive restarts. It also provided detailed reporting on extension load orders, memory overhead, and patch traps, allowing users to see precisely how much system heap space each extension claimed at startup.

MacsBug

MacsBug (Motorola Advanced Computer System Debugger) was Apple’s official low-level, assembly-language debugger. Installed directly into the System Folder, it could be invoked automatically during a system crash or manually via the programmer’s key combo (Command + Power).

For advanced users and developers diagnosing memory leaks, MacsBug offered indispensable heap-inspection commands:

  • heap: Checked the validity of the current heap zone.
  • checkheap: Verified the integrity of heap headers to detect if an extension had written past its allocated memory block.
  • dh (Dump Heap): Listed every memory block in the System Heap, revealing whether an extension repeatedly allocated memory without freeing it.
  • hx: Displayed detailed heap statistics, helping detect heap fragmentation caused by poorly designed background extensions.

ZoneRanger

ZoneRanger, created by Glenn Anderson, was a specialized graphical heap analysis utility. Unlike MacsBug's text-only environment, ZoneRanger provided a visual map of the Mac OS 9 memory space, including the System Heap, application heaps, and temporary memory.

It was widely used to catch memory leaks because it tracked allocations over time. Users could launch ZoneRanger, perform system actions, and observe if a specific extension's allocated blocks within the System Heap were growing indefinitely, providing clear visual evidence of a leak.

Peek-a-Boo

Peek-a-Boo served as the precursor to modern process monitors like macOS Activity Monitor. It provided a live, graphical overview of all running processes, background tasks, and system extensions.

Peek-a-Boo displayed real-time metrics for CPU usage, process priority, and dynamic memory consumption. By monitoring memory allocation numbers while interacting with the OS, users could watch which background extension or faceless background application (FBA) was steadily consuming system resources without returning them to the free memory pool.

Apple Extensions Manager

Included natively with Mac OS 9, the Extensions Manager was the first line of defense. While it lacked deep memory-profiling capabilities, it allowed users to toggle individual extensions, control panels, and startup items on or off, or revert to the pristine "Mac OS 9 All" or "Mac OS 9 Base" sets.

By comparing system heap availability in the "About This Computer" window between the Base set and custom configurations, users could confirm whether an auxiliary extension was progressively diminishing available memory.