[ruby-core:23492] [Bug #1484] Ruby 1.8.6_p368 and Ruby 1.8.7_p160 have threading regressions

[ruby-core:23492] [Bug #1484] Ruby 1.8.6_p368 and Ruby 1.8.7_p160 have threading regressions

[Hans de Graaff]

Bug #1484: Ruby 1.8.6_p368 and Ruby 1.8.7_p160 have threading regressions
http://redmine.ruby-lang.org/issues/show/1484

Author: Hans de Graaff
Status: Open, Priority: Normal
ruby -v: 1.8.6_p368, ruby 1.8.7_p160

Changes introduced in ruby 1.8.6_368 and ruby 1.8.7_p160 have regressions in the way they handle threading.

The following bug report for Capistrano details the regression: https://capistrano.lighthouseapp.com/projects/8716/tickets/79-capistrano-hangs-on-shell-command-for-many-computers-on-ruby-186-p368#ticket-79-22

Basically, when trying to deploy to more than one machine capistrano now hangs while eating up all CPU, instead of actually running the deployment tasks. Deploying to a single machine or deploying with e.g. ruby 1.8.7_p72 works fine.


----------------------------------------
http://redmine.ruby-lang.org

[ruby-core:23498] Re: [Bug #1484] Ruby 1.8.6_p368 and Ruby 1.8.7_p160have threading regressions

[John Carter]

On Mon, 18 May 2009, Hans de Graaff wrote:

> Bug #1484: Ruby 1.8.6_p368 and Ruby 1.8.7_p160 have threading regressions
> http://redmine.ruby-lang.org/issues/show/1484

Possibly a duplicate of
   http://redmine.ruby-lang.org/issues/show/1471




John Carter                             Phone : (64)(3) 358 6639
Tait Electronics                        Fax   : (64)(3) 359 4632
PO Box 1645 Christchurch                Email : john.carter@tait.co.nz
New Zealand

[ruby-core:24212] [Bug #1484] Ruby 1.8.6_p368 and Ruby 1.8.7_p160 have threading regressions

[Roger Pack]

Issue #1484 has been updated by Roger Pack.


>Basically, when trying to deploy to more than one machine capistrano now hangs while eating up all CPU, instead of actually running the deployment tasks. Deploying to a single machine or deploying with e.g. ruby 1.8.7_p72 works fine.

Is this still the case?
=r
----------------------------------------
http://redmine.ruby-lang.org/issues/show/1484

----------------------------------------
http://redmine.ruby-lang.org

[ruby-core:24220] Re: [Bug #1484] Ruby 1.8.6_p368 and Ruby 1.8.7_p160 have threading regressions

[Luis Lavena]

On Wed, Jul 8, 2009 at 5:24 PM, Roger Pack<redmine@ruby-lang.org> wrote:
> Issue #1484 has been updated by Roger Pack.
>
>
>>Basically, when trying to deploy to more than one machine capistrano now hangs while eating up all CPU, instead of actually running the deployment tasks. Deploying to a single machine or deploying with e.g. ruby 1.8.7_p72 works fine.
>
> Is this still the case?
> =r

I see similar problems with all threading related tasks on Mongrel and
sqlite3-ruby threaded tests.

Could be a duplicate of the other bug report.
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry

[ruby-core:24231] [Bug #1484] Ruby 1.8.6_p368 and Ruby 1.8.7_p160 have threading regressions

[Hans de Graaff]

Issue #1484 has been updated by Hans de Graaff.


http://redmine.ruby-lang.org/issues/show/1471 contains some discussion and patches that I thought were successfull, but it seems in my initial testing I was lucky or not careful enough. In any case I'm still seeing this problem with capistrano deployments when deploying to more than one machine at the time.
----------------------------------------
http://redmine.ruby-lang.org/issues/show/1484

----------------------------------------
http://redmine.ruby-lang.org

[ruby-core:25120] [Bug #1484] Ruby 1.8.6_p368 and Ruby 1.8.7_p160 have threading regressions

[Daniel Azuma]

Issue #1484 has been updated by Daniel Azuma.


I just reported http://redmine.ruby-lang.org/issues/show/1993 against 1.8.7, which looks like it's the same issue. (Sorry, I should have looked through the bug lists of the other versions-- I had thought this was 1.8.7 specific.) That other report has some analysis of rb_thread_schedule() that I think explains why this is happening. See also http://www.daniel-azuma.com/blog/view/z2ysbx0e4c3it9/ruby_1_8_7_io_select_threading_bug
----------------------------------------
http://redmine.ruby-lang.org/issues/show/1484

----------------------------------------
http://redmine.ruby-lang.org

[ruby-core:25250] [Bug #1484] Ruby 1.8.6_p368 and Ruby 1.8.7_p160 have threading regressions

[Hongli Lai]

Issue #1484 has been updated by Hongli Lai.


Hi guys, any updates on this ticket? Has it been fixed yet?
----------------------------------------
http://redmine.ruby-lang.org/issues/show/1484

----------------------------------------
http://redmine.ruby-lang.org

[ruby-core:25450] [Bug #1484] Ruby 1.8.6_p368 and Ruby 1.8.7_p160 have threading regressions

[Hans de Graaff]

Issue #1484 has been updated by Hans de Graaff.


As far as I know this has not been fixed yet, but net-ssh-2.0.14 contains a workaround that works with capistrano.
----------------------------------------
http://redmine.ruby-lang.org/issues/show/1484

----------------------------------------
http://redmine.ruby-lang.org