General

Profile

mxey (Maximilian Gass)

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 0 2 2

Activity

06/13/2010

08:31 PM Ruby master Feature #3436 (Closed): Spawn the timer thread lazily
=begin
As discussed in http://redmine.ruby-lang.org/issues/show/1820, Ruby 1.9.1
always spawns a timer thread whi... mxey (Maximilian Gass)

02/05/2010

06:49 PM Backport191 Bug #1820: Always spawns a thread that loops on the futex syscall
=begin
It is not using 100% of one core, not at all. But it causes frequent wakeups that prevent the CPU from going ... mxey (Maximilian Gass)

02/04/2010

05:59 PM Backport191 Bug #1820: Always spawns a thread that loops on the futex syscall
=begin
I see no problem with spawning an extra thread to handle signals. But if that is true, the extra thread shoul... mxey (Maximilian Gass)

07/28/2009

04:12 AM Backport191 Bug #1820 (Rejected): Always spawns a thread that loops on the futex syscall
=begin
Starting with Ruby 1.9, every Ruby process starts two threads.
One of these is looping on the futex syscal... mxey (Maximilian Gass)

Also available in: Atom