Memory leaks in 3.4.1?

[benjaminjackson]

I'm using the gem to run a ton of queries and see my memory grow to gigabytes, which I've tracked down in Instruments to the YAJL JSON parse calls in the Twitter gem. Any idea what's going on, or how I might fix this?

[stve]

Can you be more specific about the leak you are seeing?

Depending upon how you are using the gem, you may want to consider disabling the identity map, as that has led to similar issues elsewhere: tweetstream/tweetstream#87

If an identity map is useful to you, you might also consider implementing an adapter like the one in this example so that you can leverage an identity map while mitigating memory consumption.

[sferik]

@benjaminjackson Did disabling the identity map fix the memory leak for you or is it still an issue?

The purpose of the identity map (or, for that matter, any cache) is to trade memory in exchange for fewer CPU cycles. Obviously, this tradeoff is not optimal for every use case, which is why we give you the ability to disable it. Arguably, it should be disabled by default, but I think the default is correct for most uses.