Sidekiq crashes with a segmentation fault under certain conditions
Created by: alitheg
We're seeing pretty frequent crashes of Sidekiq, necessitating a restart of the service. We're not sure what the exact conditions are but it seems to be to do with a particular repository (the last job message in the Sidekiq log always lists the same repository as its target). It looks very like this issue:
https://github.com/libgit2/rugged/issues/384
Which makes me think that we've introduced a condition in our repository which trips up the version of rugged which was upgraded to in 7.2.
We're using 7.4.3.