zed-industries/zed · error

Failed to create a Ping.

Error message

Failed to create a Ping.

What it means

PriorityQueueCalloopReceiver::new calls calloop::ping::make_ping to build the wakeup mechanism for the queue; make_ping returned Err (pipe/eventfd creation failed, usually fd exhaustion) and the expect panics before the queue can be used.

Source

Thrown at crates/gpui_linux/src/linux/dispatcher.rs:194

        res
    }
}

impl<T> Drop for PriorityQueueCalloopSender<T> {
    fn drop(&mut self) {
        self.ping.ping();
    }
}

pub struct PriorityQueueCalloopReceiver<T> {
    receiver: PriorityQueueReceiver<T>,
    source: calloop::ping::PingSource,
    ping: calloop::ping::Ping,
}

impl<T> PriorityQueueCalloopReceiver<T> {
    pub fn new() -> (PriorityQueueCalloopSender<T>, Self) {
        let (ping, source) = calloop::ping::make_ping().expect("Failed to create a Ping.");

        let (tx, rx) = PriorityQueueReceiver::new();

        (
            PriorityQueueCalloopSender::new(tx, ping.clone()),
            Self {
                receiver: rx,
                source,
                ping,
            },
        )
    }
}

use calloop::channel::Event;

#[derive(Debug)]
pub struct ChannelError(calloop::ping::PingError);

View on GitHub (pinned to f4178619ac)

Solutions

1. Check file descriptor limits (ulimit -n) and fix fd leaks
2. Retry queue creation after resources free up
3. Fall back to a polling-based queue without ping if eventfd is unavailable

When it happens

Trigger: Thrown at crates/gpui_linux/src/linux/dispatcher.rs:194 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of zed-industries/zed@f4178619ac (2026-08-20). Data as JSON: /api/errors/2b4783ad45a6e898. Report an issue: GitHub.