I believe I've run into a bug while trying to get #119 to work. The following code causes the ruby process to hang, eventually throwing Ruby stack level too deep
Ruby stack level too deep
it "should play nicely with dup" do
o = Object.new
@kaiwren do you have time to look at this?
+1, encountered this today.
@dchelimsky Sure, I will, no problem.
Hey @preethiramdev, this was the issue I was telling you about.
Just for a little more insight, this seems to basically cause a fork bomb until all memory is exhausted. I recommend testing this with a wrapper script like this to limit the amount of memory it can consume:
# 500 MB
ulimit -Sv 500000
@tfwright Ive been able to replicate this. Will probably not get much done over the weekend tho so will start looking into this on Monday.
@jmazzi Will try that
@dchelimsky I'm helping a few of my colleagues get used to contributing via #124 and #120 - it's taking a little longer than expected. If this is a blocker for an upcoming release, please let me know and I'll fix them myself.
This is not a blocker. We can release this fix as a patch release of 2.9 or 2.10, whichever is current when this gets done.
Replicating Issue #120
Issue #120: Under any_instance, modify #dup to remove the mock proxy
See pull request #138
Closed by #138.
@jmazzi You're welcome. In fact, I'm sorry I took this long to get this sorted. I hope it wasn't too much of an inconvenience.
@kaiwren nope, we worked around it.