Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Arti Arti
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 259
    • Issues 259
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 23
    • Merge requests 23
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • ArtiArti
  • Issues
  • #572
Closed
Open
Issue created Sep 07, 2022 by driverme@driverme

dropping TorClient will burn cpu

Summary

Dropping TorClient will stuck in tor_rtcompat::scheduler::TaskSchedule::sleep_until_wallclock() and burning cpu

Steps to reproduce:

Change the example of read.rs as following


/// readme.rs
#[tokio::main]
async fn main() -> Result<()> { 
    old_main().await?;
    println!("sleep forever");
    tokio::time::sleep(std::time::Duration::from_secs(999999)).await; // burning cpu here
    Ok(())
}

async fn old_main() -> Result<()> {
    ...
}

What is the current bug behavior?

What is the expected behavior?

Environment

Possible fixes:

Assignee
Assign to
Time tracking