-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Integration] C Data Interface integration segmentation fault with Java and other runtimes #38684
Comments
This bug is still popping up on a semi-regular basis - https://github.com/apache/arrow-rs/actions/runs/6955964090/attempts/1?pr=5111 @pitrou FYI |
Yes, I've seen it recently as well. For now we're not able to point at a particular problem. It might be an unfortunate effect of several managed runtimes (.Net, Java, Go) competing for resources. I managed to reproduce it locally once and got the following traceback, but I don't really know what to make of it except stare at the ghastly nesting of signal handlers :-) |
Oh my, that is spicy 😅 |
A potential culprit here: Edit: no, it seems to be a red herring, though it's probably a good idea to enable this option anyway. |
By disabling Java signals and the Go backend I get a more palatable stack trace:
|
This seems generally related to C#. |
…38846) ### Rationale for this change C Data Interface integration tests sometimes crash with a complicated traceback involving Java, Go and C# signal handlers. ### What changes are included in this PR? * Update JDK version in integration build * Disable signal-based memory management in the JVM so as to improve cooperation with other runtimes * Set memory limits to the various managed runtimes (Java, .Net, Go) * Enable some checks in the Go runtime * Enable debug allocator in Arrow Java ### Are these changes tested? Yes. I am not able to reproduce any sporadic crash using these changes. ### Are there any user-facing changes? No. * Closes: #38684 Authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
…ing (apache#38846) ### Rationale for this change C Data Interface integration tests sometimes crash with a complicated traceback involving Java, Go and C# signal handlers. ### What changes are included in this PR? * Update JDK version in integration build * Disable signal-based memory management in the JVM so as to improve cooperation with other runtimes * Set memory limits to the various managed runtimes (Java, .Net, Go) * Enable some checks in the Go runtime * Enable debug allocator in Arrow Java ### Are these changes tested? Yes. I am not able to reproduce any sporadic crash using these changes. ### Are there any user-facing changes? No. * Closes: apache#38684 Authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
Describe the bug, including details regarding any error messages, version, and platform.
Over the last few weeks I've noticed intermittent segfaults when running the python integration tests.
It is possible this is something specific to the arrow-rs testing setup, but thought I would flag in case there is something else going on here
https://github.com/apache/arrow-rs/actions/runs/6850128392/job/18623690451
https://github.com/apache/arrow-rs/actions/runs/6837344006/job/18593220363
https://github.com/apache/arrow-rs/actions/runs/6692138689/job/18180724463
Component(s)
Archery
The text was updated successfully, but these errors were encountered: