hsbt_away changed the topic of #ruby-core to: check the latest release candidate for 1.9.1 release ftp.ruby-lang.org:/home/yugui/ruby-1.9.1-r26021+1.tar.bz2
kosaki2_ has joined #ruby-core
kosaki2 has quit [Read error: Connection reset by peer]
nagachika has joined #ruby-core
<_ko1>
What name of the world zombies and ghost?
<_ko1>
now I named halloween_heap.
shinnya has joined #ruby-core
<kosaki2_>
What is halloween_heap? How work?
ortuna has joined #ruby-core
headius has joined #ruby-core
<_ko1>
cache storage
shinnya has quit [Ping timeout: 272 seconds]
nari has joined #ruby-core
<zzak>
lol
nari has quit [Ping timeout: 260 seconds]
DanKnox is now known as DanKnox_away
DanKnox_away is now known as DanKnox
Domon has joined #ruby-core
DanKnox is now known as DanKnox_away
Domon__ has joined #ruby-core
Domon has quit [Ping timeout: 240 seconds]
nari has joined #ruby-core
kosaki2_ has quit [Remote host closed the connection]
kosaki2 has joined #ruby-core
ortuna has quit [Quit: WeeChat 0.4.1]
kosaki2 has quit [Ping timeout: 272 seconds]
headius has quit [Quit: headius]
ZachBeta has joined #ruby-core
<znz_jp>
biff: [ruby-changes:31314] zzak:r43393 (trunk): * file.c: [DOC] fix rdoc format of File#expand_path from r43386 - http://mla.n-z.jp/?ruby-changes=31314
ZachBeta has quit [Quit: Computer has gone to sleep.]
<zzak>
_ko1: ping!
<_ko1>
pong
<zzak>
_ko1: does ext/objspace trace_object_allocations_clear call GC?
<zzak>
someone wrote: "Objects that were allocated while tracing was enabled cannot be garbage-collected until ::trace_object_allocations_clear is called"
<_ko1>
??
<_ko1>
let me a time
<_ko1>
to translate :)
<_ko1>
what means "enabled cannot be GC"
<_ko1>
?
<zzak>
let me try to rephrase
ZachBeta has joined #ruby-core
<zzak>
Objects are not GC if allocated after trace_object_allocations_start is called
<zzak>
unless trace_object_allocations_clear is called
<_ko1>
you can try :)
<_ko1>
if so, it is bug
<zzak>
so not spec, they should get GC either way?
<_ko1>
you mean "Objects are collected with GC" ?
<_ko1>
Yes.
<zzak>
yeah
<_ko1>
require 'objspace'
<_ko1>
ObjectSpace.trace_object_allocations{
<_ko1>
loop{''}
<_ko1>
}
<_ko1>
try it
<zzak>
so this statement is false: "Objects are not GC if allocated after trace_object_allocations_start is called"
<zzak>
_ko1: it hangs :)
marcandre has quit [Read error: Connection reset by peer]
<_ko1>
infinite loop
<_ko1>
see the memory usage from OS
marcandre has joined #ruby-core
<zzak>
_ko1: 100% cpu 15mb ram
ZachBeta has quit [Quit: Computer has gone to sleep.]
<_ko1>
but not explosion
<_ko1>
right?
<_ko1>
GC is active.
<zzak>
its true
<zzak>
the statement is a lie
<_ko1>
yes
<zzak>
i will update the ticket, thank you so much!
<cout>
zzak: I think you made up the part about the mummies :)
ZachBeta has quit [Quit: Computer has gone to sleep.]
judofyr has quit [Remote host closed the connection]
ZachBeta has joined #ruby-core
judofyr has joined #ruby-core
tylersmith has joined #ruby-core
tylersmith has quit [Ping timeout: 260 seconds]
<zzak>
hsbt_: ping
<znz_jp>
biff: [ruby-changes:31320] tmm1:r43399 (trunk): * gc.c: Rename free_min to min_free_slots and free_min_page to max_free_slots. The algorithm for heap growth is: - http://mla.n-z.jp/?ruby-changes=31320