-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
Ruby Segmentation Fault #3352
Comments
@blowmage the grpc team is unable to reproduce the segfault in grpc/grpc#11762:
Could you provide more detail or another case that they might be able to reproduce? |
I can't. We haven't determined any antecedent for the segfaults. They seem to happen randomly. |
K. Thanks Mike! |
@blowmage Can you provide code that (sometimes) shows it? |
The code is the same as on grpc/grpc#11762. |
I am trying to use valgrind to see whether the c extension has some memory problem. |
Fixed in #3560. |
Seems like this is a bug of grpc. |
@TeBoring @apolcyn The equivalent gRPC issue (grpc/grpc#11762) was closed because "the probable cause" seemed to be in protobuf. Is there a way to determine the root cause and re-open the appropriate issue? |
From the c level backtrace, it seems the bug is in grpc. |
I agree that from the stack trace, it does appear to be coming from within grpc. Is the crash described in grpc/grpc#11762 still occuring? If so, I think we should look into. But it would be really helpful to get a repro case in order to dig in. |
#3649 may give some hint. |
ok, good idea I can look into the grpc crash using the repro in grpc/grpc#11762 and GC stress modes. |
To update here, I'm not seeing the segfault but I am seeing a different and suspicious error that looks like it's related to grpc. Using a variant of the script from grpc/grpc#11762 (running from the Running on mac, from the
When turning on
|
Running under I can't say if I am seeing the root cause of the original issue here, but I suspect it is related, WIP on this.... |
grpc/grpc#12842 fixes the issue mentioned in my comment above, this was just released in |
With the |
Is the stack trace here relevant? |
This issue definitely came from within grpc... I am not sure what the root of it is atm. |
I have a Segmentation Fault report. This has happened while performance testing changes to the Google Cloud Pub/Sub Ruby library. This happened right after the segfault reported in grpc/grpc#11762.
System details:
segfault details
The text was updated successfully, but these errors were encountered: