Windows: endpoints hang or crash when several bind at once (concurrent WMI default-route queries?)
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- rust
- Domain
- backend, networking
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Rust
- Stars
- 34
- Forks
- 56
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from n0-computer/net-tools
-
Difficulty 1/5 1-3 hours Newbie friendliness 33/100
n0-computer/net-tools#280 ·
Maintainers usually reply within 2 days
-
netwatch: objc2-system-configuration with default features pulls objc2-security into every macOS buildPossibly taken @flub claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
n0-computer/net-tools#278 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
n0-computer/net-tools#276 ·
Maintainers usually reply within 2 days
-
netwatch never turns on noq-udp's Apple fast path, so iroh's `fast-apple-datapath` does nothingOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
n0-computer/net-tools#272 ·
Maintainers usually reply within 2 days
-
portmapper: synchronous HomeRouter lookup blocks the Tokio workerPossibly taken @TNTcraftHIM claimed this 19 days ago. Openready-for-pr
Difficulty 3/5 1-2 days Newbie friendliness 50/100
n0-computer/net-tools#266 · 1 comment ·
Maintainers usually reply within 2 days
All issues in n0-computer/net-tools
Similar issues
-
area:web kind:bug priority:p2 ready
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
sims1253/r-typeshed#140 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
storytold/craft-libs#2867 ·
Maintainers usually reply within 1 day
-
help wanted needs investigation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 62/100