Excessive CPU usage in windows tor_cond_t code?

On #33411 (moved), gvanem reports excdessive CPU consumption in the windows tor_cond_t code. We should see if we can fix that.

changed milestone to %Tor: unspecified

added 044-deferred backport? component::core tor/tor milestone::Tor: unspecified priority::medium regression severity::normal status::new type::defect windows labels

Trac:
Cc: N/A to gvanem

Just wanted to link my report about this at tor-relays mailing list. Seems like it's confirmed by others as well. https://lists.torproject.org/pipermail/tor-relays/2020-April/018408.html Although this isn't a show stopper we hope to get a fix in future releases so relays running on Windows can be put to work for a longer time without interventions.

Trac:
Username: scullcactus

Trac:
Keywords: backport? deleted, backport? regression windows added

Add 044-must to all "regression" tickets in 0.4.4

Trac:
Keywords: backport? regression windows deleted, backport?, windows, regression added

Bulk-remove tickets from 0.4.4. Add the 044-deferred label to them.

Trac:
Keywords: N/A deleted, 044-deferred added
Milestone: Tor: 0.4.4.x-final to Tor: unspecified

moved to tpo/core/tor#33554 (closed)