Skip to content

no mutex in shutdown #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 3 commits into from
Closed

no mutex in shutdown #42

wants to merge 3 commits into from

Conversation

jjb
Copy link
Owner

@jjb jjb commented Jan 15, 2024

  • shutdown outside of the handler
  • wip

jjb added 3 commits January 14, 2024 18:31
@jjb
shutdown outside of the handler
92427ed 
because, i think but haven't totally verified, rufus will create
mutexts sometimes which is not allowed in a signal handler
@jjb
wip
526117b
@jjb
comments, and flushing stdout
83c1632
@jjb jjb changed the title no mutex in shutdown without loop no mutex in shutdown Jan 15, 2024
@jjb
Copy link
Owner Author

jjb commented Jan 15, 2024 

ruby-clock-2.0.1/lib/ruby-clock.rb:28:in `write': deadlock; recursive locking (ThreadError)
	gems/ruby-clock-2.0.1/lib/ruby-clock.rb:28:in `puts'
	gems/ruby-clock-2.0.1/lib/ruby-clock.rb:28:in `puts'
	gems/ruby-clock-2.0.1/lib/ruby-clock.rb:28:in `shutdown'
	gems/ruby-clock-2.0.1/lib/ruby-clock.rb:37:in `block (2 levels) in listen_to_signals'
	gems/ruby-clock-2.0.1/lib/ruby-clock.rb:53:in `write'
	gems/ruby-clock-2.0.1/lib/ruby-clock.rb:53:in `puts'
	gems/ruby-clock-2.0.1/lib/ruby-clock.rb:53:in `puts'
	gems/ruby-clock-2.0.1/lib/ruby-clock.rb:53:in `run_jobs'
	gems/ruby-clock-2.0.1/exe/clock:84:in `<top (required)>'

@jjb jjb closed this Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@jjb