Closed zettam closed 9 years ago
How many times did you trigger the handler, and does the memory grow infinitely? Ruby is a garbage collected language; unless memory usage grows without bound there's no sign for a leak.
I'm spamming the chatroom with random stuff. Then when I say "hello" it doesn't even respond for a while. Takes minutes for the bot to respond.
Also possible to see (when logged) that incoming messages are coming very very late (seconds to minutes late) so that might be the reason of this latency. However, growing in memory is another issue, maybe related.
You're really throwing too many variables together to make this a useful way of diagnosing anything. "Spamming random stuff" is likely to get you into throttling on both your client's and your server's end, so delays don't mean much. You haven't addressed either of my questions, so the memory growth is still just an unexplained artifact.
Considering that people use Cinch to handle tens of thousands messages a day, and don't see gigabytes of memory usage or minutes of delays, I don't think that Cinch is overwhelmed by or leaking memory because of simply receiving messages.
Timed out. Reopen if you can provide more details.
I am using the simple hello.rb on my digital ocean droplet. I can see that every time the bot responds me, it's memory usage increases a bit.
Is this a bug, or am I missing something?