Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Crash running Sidekiq #2132

tmornini opened this Issue Jan 22, 2013 · 8 comments


None yet
3 participants

tmornini commented Jan 22, 2013

Hey guys. Tried using Rubinius to improve our Sidekiq processing.



brixen commented Jan 22, 2013

@tmornini I commented on the gist, but I'll recomment here:

The memory violation appears to happen inside yajl doing a malloc call. Until the EM issues is addressed, it's not easy to determine whether yajl got bad data or if there's some issue with Rubinius C-API that yajl is using.


dbussink commented Jan 23, 2013

Looks like this project shows some issues, also #2102. Do you think there's a way we could run those specs and this code to make sure it all works well?


tmornini commented Mar 1, 2013

Sorry for the delay, have been seriously head-down.

I'll make the code available in a few of weeks. :-)


dbussink commented Apr 11, 2013

Did you get to setting this up somewhere? We've also fixed some issues that showed with using Sidekiq, if you could try again to see if there are still issues that would be great!


dbussink commented May 23, 2013

Does this issue still happen? We've fixed a bunch of additional issues that showed up with Sidekiq that could result in crashes.


tmornini commented Jul 15, 2013

Unknown. We're no longer using Sidekiq. Feel free to close.

@dbussink dbussink closed this Jul 15, 2013


dbussink commented Jul 15, 2013

Ok, closing this one then. If you encounter something with a different sidekiq app then, please open a new issue.


brixen commented Jul 15, 2013

@tmornini out of curiosity, did you switch to something instead of Sidekiq or are you no longer using that functionality?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment