Skip to content
This repository has been archived by the owner on Apr 13, 2019. It is now read-only.

bot.quit gives deadlock error #17

Closed
igorw opened this issue Sep 8, 2010 · 3 comments
Closed

bot.quit gives deadlock error #17

igorw opened this issue Sep 8, 2010 · 3 comments
Assignees
Labels

Comments

@igorw
Copy link

igorw commented Sep 8, 2010

When running the following code

require 'cinch'

bot = Cinch::Bot.new do
    configure do |c|
        c.nick = "IgorBot"
        c.server = "irc.freenode.org"
        c.channels = ["#mybotchannel"]
    end

    # quit
    on :message, "!quit" do |m|
        bot.quit
    end
end

bot.start

and sending the !quit command, I receive following error:

/home/igor/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/thread.rb:185:in sleep': deadlock detected (fatal) from /home/igor/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/thread.rb:185:inblock in pop'
from internal:prelude:10:in synchronize' from /home/igor/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/thread.rb:180:inpop'
from /home/igor/.rvm/gems/ruby-1.9.2-p0/gems/cinch-1.0.2/lib/cinch/message_queue.rb:52:in process!' from /home/igor/.rvm/gems/ruby-1.9.2-p0/gems/cinch-1.0.2/lib/cinch/irc.rb:58:inconnect'
from /home/igor/.rvm/gems/ruby-1.9.2-p0/gems/cinch-1.0.2/lib/cinch/bot.rb:404:in start' from mybot.rb:12:in

'

@dominikh
Copy link
Member

dominikh commented Sep 8, 2010

Thanks for reporting the bug.

I am able to reproduce this here and already have a solution in mind. The bug, however, has low priority right now, mostly because it doesn't affect the actual running of the bot.

It will be fixed in the next patch or minor release, though.

@igorw
Copy link
Author

igorw commented Sep 8, 2010

Awesome, thanks!

@dominikh
Copy link
Member

dominikh commented Dec 8, 2010

Merge branch 'fix-quit_deadlock'

Closed by 1a95ccd

Conflicts:
lib/cinch/bot.rb

@ghost ghost assigned dominikh Apr 10, 2011
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants