http://bugs.winehq.org/show_bug.cgi?id=60251 --- Comment #5 from Kazim <aktaskazimcan0@gmail.com> ---
Are you sure about that? CoCreateInstance() is essentially a malloc() call but ConnectServer() taking a long time would explain it. It resolves the hostname which will time out if there's no response.
Good question — I can answer that from the same reproducer's per-step timestamps, though I only posted the summary table above, not the raw per-call breakdown. Across every run I did (both Wine builds, TUN on and off): the elapsed time printed right after ConnectServer() is always within 0-2ms of the value printed right after CoCreateInstance() — e.g. 29830ms then 29830ms, 29821ms then 29821ms, 14ms then 16ms, 17ms then 17ms. So ConnectServer() itself is consistently near-instant (it fails fast with WBEM_E_INVALID_NAMESPACE either way) — it's CoCreateInstance() that swings from ~15ms to ~29800ms depending on TUN state, a ~2000x difference that has nothing to do with ConnectServer()'s hostname resolution. That matches your point about CLSCTX_INPROC_SERVER not needing the network — which is why I flagged it as surprising rather than claiming to understand the mechanism. Happy to strace just the CoCreateInstance() window with TUN on to see which syscall it's blocked in, or paste the full per-run logs here if that's easier to review. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.