skhrshin (Shintaro Sakahara)

	open	closed	Total
Assigned issues	0	0	0
Reported issues	0	1	1

09:35 AM Ruby master Bug #20485: Simple use of Fiber makes GC leak objects with singleton method: I tried looping with `100.times` in a more complex case that I created in the middle of the entire investigation of a... skhrshin (Shintaro Sakahara)
08:25 AM Ruby master Bug #20485: Simple use of Fiber makes GC leak objects with singleton method: I asked my co-workers to try this script and some of them gave me their results. The following table includes my resu... skhrshin (Shintaro Sakahara)
04:33 AM Ruby master Bug #20485: Simple use of Fiber makes GC leak objects with singleton method: Do you mean this is fixed in trunk? Or are you saying this shouldn't happen on Ruby 3.3.1? If latter, that is not cor... skhrshin (Shintaro Sakahara)

09:09 AM Ruby master Bug #20485: Simple use of Fiber makes GC leak objects with singleton method: I confirmed that all of `1.times`, `[1].each` and `Mutex.new.synchronize` versions reproduce the problem on Ruby 3.2.4. skhrshin (Shintaro Sakahara)
08:52 AM Ruby master Bug #20485: Simple use of Fiber makes GC leak objects with singleton method: Changing `1.times` to `[1].each` could reproduce the problem on Ruby 3.3.1 too. skhrshin (Shintaro Sakahara)
08:46 AM Ruby master Bug #20485: Simple use of Fiber makes GC leak objects with singleton method: Update: To reproduce this issue with Ruby 3.3.1, Mutex is necessary. skhrshin (Shintaro Sakahara)
06:09 AM Ruby master Bug #20485: Simple use of Fiber makes GC leak objects with singleton method: Update: Using Mutex was not necessary. skhrshin (Shintaro Sakahara)
03:39 AM Ruby master Bug #20485 (Closed): Simple use of Fiber makes GC leak objects with singleton method: I found a possible memory leak which occurs only when several conditions are met.
The code to reproduce the proble... skhrshin (Shintaro Sakahara)

Also available in: Atom

Ruby Issue Tracking System