@wycats Lots of sidekiq users are reporting leaks in Ruby 2.1 not in 2.0.
-
-
-
@mperham We've seen very severe leaks in 2.1 too. Let's escalate this?
End of conversation
New conversation -
-
-
@wycats we didn’t quite confirm, but it looked like a mem leak, when we deployed travis-api on 2.1 the other day, so we reverted -
@svenfuchs We've been chasing phantoms for a couple days and it looks like Ruby 2.1 is the root cause.
End of conversation
New conversation -
-
-
@wycats we've been seeing jumps in memory with@SimplyBuiltThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wycats I've seen a few reports from customersThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wycats I saw mem increase in going from 1.9.2 to 2.0.0.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wycats i've heard this, yesThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wycats I’ve heard anecdotal stories about increased base use, haven’t heard about leaks. Havent used it yet, all our stuff is 2.0 currentlyThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.