From: "ko1 (Koichi Sasada)" Date: 2012-11-26T09:00:39+09:00 Subject: [ruby-core:50112] [ruby-trunk - Bug #1152] profiler.rb is not concurrent-execution threadsafe Issue #1152 has been updated by ko1 (Koichi Sasada). Assignee changed from ko1 (Koichi Sasada) to nobu (Nobuyoshi Nakada) nobu, could you check it? ---------------------------------------- Bug #1152: profiler.rb is not concurrent-execution threadsafe https://bugs.ruby-lang.org/issues/1152#change-33893 Author: headius (Charles Nutter) Status: Assigned Priority: Normal Assignee: nobu (Nobuyoshi Nakada) Category: lib Target version: 2.0.0 ruby -v: all versions 1.8.6 and up =begin The library profiler.rb uses class variables to store data without wrapping them in mutexes. On current C Ruby, this may only rarely cause a problem, but as more and more code is allowed to run in parallel it's going to lead to issues. If I or other JRuby community members have a chance, we'll try to make it thread-safe, but I wanted to file this issue to ensure it's out there. The library is also largely unchanged in 1.9.1. See http://jira.codehaus.org/browse/JRUBY-2133 for the (admittedly sparse) JRuby issue. =end -- http://bugs.ruby-lang.org/