From: Delano Mandelbaum Date: 2011-02-11T17:49:32+09:00 Subject: [ruby-core:35192] [Ruby 1.9-Bug#4389][Open] "pointer being freed was not allocated" error after setting instance variable in metaclass for Thread.current Bug #4389: "pointer being freed was not allocated" error after setting instance variable in metaclass for Thread.current http://redmine.ruby-lang.org/issues/show/4389 Author: Delano Mandelbaum Status: Open, Priority: Normal Target version: 1.9.2 ruby -v: ruby 1.9.2p136 (2010-12-25) [x86_64-darwin10.6.0] To recreate: class Thread def metaclass class << self; self; end; end end Thread.current.metaclass.instance_variable_set("@data", :data) exit Result: ruby(28425,0x7fff70bc9ca0) malloc: *** error for object 0x100400000: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug Ruby 1.8.7, 1.9.1 are not affected. Reproduced on: Darwin hostname 10.6.0 Darwin Kernel Version 10.6.0: Wed Nov 10 18:13:17 PST 2010; root:xnu-1504.9.26~3/RELEASE_I386 i386 Linux hostname 2.6.32.16-linode28 #1 SMP Sun Jul 25 21:32:42 UTC 2010 i686 GNU/Linux ---------------------------------------- http://redmine.ruby-lang.org