Joel Pearson wrote in post #1087112:
> I've also seen that error before when the browser is closed in the
> middle of doing something. Maybe "br.close" is triggering while the
> thread is still doing something?

How can it be triggered without reason?

-- 
Posted via http://www.ruby-forum.com/.