The above seems to work fine on -head, although I do see the leak with Thin on head. Ask Marc?
>
> --
> You received this message because you are subscribed to the Google Groups "EventMachine" group.
> To post to this group, send email to eventm...@googlegroups.com.
> To unsubscribe from this group, send email to eventmachine...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/eventmachine?hl=en.
>
Another data point, I can reproduce this using EventMachine with
Rainbows! 0.95.1 but not with other concurrency models such as
Rev or FiberSpawn (but I did find something odd with ThreadSpawn
which appears to be a Ruby bug :x)
I've tested with 1.9.2-rc2 on x86_64 and EM 0.12.10
--
Eric Wong
Does the bug hide with 1.8?
Would you be able to save me some time and isolate the parser and see if it's occurring there?
>
> --
> Eric Wong
Seems to be stable on 1.9 actually.
Trying to create a minimal case for EM that replicates this, but failing.
Apologies for the spam, reproduced as a standalone test, I will publish details once I've paired this back.
I've now updated the ticket on rubys redmine, this is a leak in ruby 1.9 with Kernel#method. Can you confirm this is the source of your leak too Eric?
Regards,
James
Yup, I can reproduce this under 1.9.2-rc2 but not 1.9.1-p378.
Thanks for isolating this, James!
--
Eric Wong
--
Eric Wong
--
You received this message because you are subscribed to the Google Groups "EventMachine" group.
To post to this group, send email to eventm...@googlegroups.com.
To unsubscribe from this group, send email to eventmachine...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/eventmachine?hl=en.