Opened 5 months ago

Last modified 2 months ago

#33554 new defect

Excessive CPU usage in windows tor_cond_t code?

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: backport?, regression, windows, 044-deferred
Cc: gvanem Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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

Child Tickets

Change History (5)

comment:1 Changed 5 months ago by nickm

Cc: gvanem added

comment:2 Changed 4 months ago by scullcactus

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.

comment:3 Changed 3 months ago by dgoulet

Keywords: regression windows added

comment:4 Changed 3 months ago by nickm

Keywords: backport? regression windowsbackport?, regression, windows

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

comment:5 Changed 2 months ago by nickm

Keywords: 044-deferred added
Milestone: Tor: 0.4.4.x-finalTor: unspecified

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

Note: See TracTickets for help on using tickets.