-
Notifications
You must be signed in to change notification settings - Fork 602
GC crash #2908
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Experienced another one on 2.2.5:
Currently looking into to see if this is caused by Nokogiri or something else. |
Another one that occurred before the one reported above:
|
I suppose the one good part here is that the issue re-occurs consistently. Now I need to figure out a way to reproduce it in a standalone environment. |
What is |
Don't know if i should open a new issue for this but it looks like a similar error trace for me...
Error occurs when Im using the sublime2 extension SublimeREPL |
@Benny1992 That's a very different issue, so probably best as a separate one. Do you have a way to reproduce that? |
okay opening a new one |
@dbussink No, it's one of our applications that is misbehaving. The proctitle is simply set to |
Output of the backtraces as shown in GDB (http://hastebin.com/raw/suyudovuga link that's a bit easier to read):
|
After compiling Nokogiri from source (to ensure that the changes made to it by @dbussink are present) I'm presented with the following segfault instead:
|
GDB backtraces of all threads: http://hastebin.com/raw/mawehegoqa |
And one with optimizations disabled: http://hastebin.com/raw/rolenakale |
Closing this one in favour of #2957 and the Nokogiri issue mentioned above as this particular case should be fixed. |
When running a production app in a multi-threaded environment the following error once in a while pops up:
Sadly I'm currently not aware what's causing it, though it might be that @dbussink's recent GC fixes solve the above issue (haven't been able to confirm that yet).
The text was updated successfully, but these errors were encountered: