I was just working on updating how curb handles exceptions in callbacks for http requests… this would have been a great read prior to doing that work. Going to see if I can go back in there and clean any thing up - thanks for this post
You won’t be alone in having memory leaks in your gem, unfortunately. Using Ruby’s C API is hard as a user, and it’s a bit of a pain from an implementor’s point of view as well.
I was just working on updating how curb handles exceptions in callbacks for http requests… this would have been a great read prior to doing that work. Going to see if I can go back in there and clean any thing up - thanks for this post
You won’t be alone in having memory leaks in your gem, unfortunately. Using Ruby’s C API is hard as a user, and it’s a bit of a pain from an implementor’s point of view as well.