Windows: endpoints hang or crash when several bind at once (concurrent WMI default-route queries?)
Los mantenedores suelen responder en 2 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 55/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- rust
- Área
- backend, networking
Línea de trabajo
Start with src/interfaces/windows.rs and inspect get_default_route, which the issue identifies as the WMI query path. Compare it with the reported GetIpForwardTable2(AF_INET) approach and check how Windows dependencies and route detection are handled. Done means concurrent endpoint binds no longer hang or crash on Windows while default route detection retains the described behavior.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the bug
We're seeing this in our project and wanted to share it in case it's useful.
On Windows, when several iroh endpoints are created at the same time in one process, Endpoint::bind()
sometimes hangs (it never returns) or the process crashes. In our CI, a test that binds five endpoints at once
on loopback failed in about 3 of every 4 runs on GitHub's Windows runners. It never fails on Linux or macOS.
This looks related to #124, but it still happens with the spawn_blocking fix from #127 (we're on 0.19.3).
The difference here is several WMI queries running at the same time, one per netmon::Monitor.
What we found:
- The hangs and crashes happen inside the WMI query that
interfaces::windows::get_default_routeruns over
COM (Win32_IP4RouteTable). With full page heap enabled, our runs stopped on freed memory inside COM during
those queries (combase!OXIDEntry::DecRefCnt,CROIDTable::ClientDeRegisterOIDFromPingServer, and once in
an already unloadedwbemprox.dll). - Initializing COM ourselves first (MTA, security) and keeping a WMI connection open didn't help.
- Reading the route table with
GetIpForwardTable2(AF_INET)and checking for a route with prefix length 0
avoids COM entirely. With only that change, the failures stopped: our Windows CI has passed every run since,
including repeated runs of the same commit.
A side note we noticed: Win32_IP4RouteTable.Name is the route's destination, not an interface name, so on
Windows default_route_interface is always "0.0.0.0". The replacement below keeps that value, so
is_major_change behaves the same. Returning the real interface (the row's InterfaceIndex) could be a
follow-up.
This is the replacement we're using in a patched copy (it drops the wmi and serde dependencies on
Windows):
fn get_default_route() -> Result<DefaultRouteDetails, Error> {
let mut table: *mut MIB_IPFORWARD_TABLE2 = std::ptr::null_mut();
// SAFETY: Windows allocates the table and returns it in `table`.
unsafe { GetIpForwardTable2(AF_INET, &mut table) }.ok()?;
// SAFETY: on success `table` points to `NumEntries` rows, read here only, and freed once below.
let found = unsafe {
let rows = std::slice::from_raw_parts((*table).Table.as_ptr(), (*table).NumEntries as usize);
let found = rows.iter().any(|row| row.DestinationPrefix.PrefixLength == 0);
FreeMibTable(table.cast());
found
};
if !found {
return Err(e!(Error::NoRoute));
}
Ok(DefaultRouteDetails { interface_name: "0.0.0.0".to_string() })
}
(still called through tokio::task::spawn_blocking, as now.)
The full change is here: https://github.com/alexpacheli/hext-remote/tree/main/vendor/netwatch (see
PATCHED.md and src/interfaces/windows.rs).
Relevant Logs
No useful trace logs: the process just stops inside the WMI query. The page heap stacks are the ones above.
Expected behavior
Several endpoints can bind at the same time on Windows without hanging or crashing.
netwatch, portmapper
Version: netwatch 0.19.3 (through iroh 1.4.1), wmi 0.18.4
Platform(s)
Desktop:
- OS: Windows Server 2025 (GitHub Actions
windows-2025runner) - Version: x86_64-pc-windows-msvc
Additional Context / Screenshots / GIFs
Happy to test a fix or provide more details. The investigation was done with the help of an AI coding
assistant; the results above (the failures and the fix) come from our CI runs.
lolwut
- This issue was created by a human that thought critically about
the issue being reported and wrote this as concisely and clearly
as they could. Taking full responsibility for the issue being
accurate. - This issue isn't slop, and is backed up by evidence.
- Lenguaje dominante
- Rust
- Estrellas
- 34
- Forks
- 56
- Merge medio
- 2 d 4 h
- PR fusionados (30 d)
- 8
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de n0-computer/net-tools
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 33/100
n0-computer/net-tools#280 ·
Los mantenedores suelen responder en 2 días
-
netwatch: objc2-system-configuration with default features pulls objc2-security into every macOS buildPosiblemente ocupada @flub la tomó hace 1 día. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 25/100
n0-computer/net-tools#278 · 2 comentarios ·
Los mantenedores suelen responder en 2 días
-
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
n0-computer/net-tools#276 ·
Los mantenedores suelen responder en 2 días
-
netwatch never turns on noq-udp's Apple fast path, so iroh's `fast-apple-datapath` does nothingAbierto
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
n0-computer/net-tools#272 ·
Los mantenedores suelen responder en 2 días
-
portmapper: synchronous HomeRouter lookup blocks the Tokio workerPosiblemente ocupada @TNTcraftHIM la tomó hace 19 días. Abiertoready-for-pr
Dificultad 3/5 1-2 días Aptitud para principiantes 50/100
n0-computer/net-tools#266 · 1 comentario ·
Los mantenedores suelen responder en 2 días
Todos los issues de n0-computer/net-tools
Issues similares
-
area:web kind:bug priority:p2 ready
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
sims1253/ry#931 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 84/100
sims1253/r-typeshed#140 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
storytold/craft-libs#2867 ·
Los mantenedores suelen responder en 1 día
-
help wanted needs investigation priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100