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
v1.13.0 causes Segmentation Faults on Windows #784
Comments
We are seeing the same thing through our build scripts. We get exit code |
The segfault is due to the change of LIBC from But the root cause is that libsass uses I opened sass/sassc-ruby#205 to move memory allocation to FFI's MemoryPointer. This fixes the segfault, but the better fix would be to add another API call to libsass, which allocates memory to be used for the string to submit. This can be more or less a simple wrapper around |
In other words, it's going to take more time and the recommended solution for now is to lock to Thanks for looking into this and submitting a patch for the |
See ffi/ffi#784 Signed-off-by: James Stocks <jstocks@chef.io>
See ffi/ffi#784 Signed-off-by: James Stocks <jstocks@chef.io>
See ffi/ffi#784 Signed-off-by: James Stocks <jstocks@chef.io>
The Keeping this open for visibility for other projects not involving Jekyll. |
ffi 0.13 crashes Ruby on windows - see ffi/ffi#784 Signed-off-by: James Stocks <jstocks@chef.io>
ffi 0.13 crashes Ruby on windows - see ffi/ffi#784 Signed-off-by: James Stocks <jstocks@chef.io>
ffi 0.13 crashes Ruby on windows - see ffi/ffi#784 Signed-off-by: James Stocks <jstocks@chef.io>
Hi @larskanis given the segfault, would it be possible to yank the 0.13 gem? |
ffi 0.13 segfaults on windows, see ffi/ffi#784
@joshcooper, @james-stocks Could you please open a new issue with the stack trace printed by ruby? I tried to find a stack trace in the links you posted to no avail. The Windows segfaults are more an issue of depending libraries than an issue of ffi. That's why I don't want to yank ffi-1.13.0. Since this particular issue has been fixed in sassc.gem I'm going to close it now |
Filed as #788 |
Our tests are failing on Windows: https://buildkite.com/chef-oss/inspec-train-master-verify/builds/395#18f8c2af-6501-4258-bdbf-0f8af87ce9e7 ``` rake aborted! SignalException: SIGSEGV ``` See ffi/ffi#784 - ffi 0.13 introduces segmentation faults. These are not ffi's fault directly, other gems that are not using ffi 100% correctly get away with it in ffi 0.12 but now crash with 0.13. Signed-off-by: James Stocks <jstocks@chef.io>
Our tests are failing on Windows: https://buildkite.com/chef-oss/inspec-train-master-verify/builds/395#18f8c2af-6501-4258-bdbf-0f8af87ce9e7 ``` rake aborted! SignalException: SIGSEGV ``` See ffi/ffi#784 - ffi 1.13 introduces segmentation faults. These are not ffi's fault directly, other gems that are not using ffi 100% correctly get away with it in ffi 1.12 but now crash with 1.13. Signed-off-by: James Stocks <jstocks@chef.io>
ffi 0.13 crashes Ruby on windows - see ffi/ffi#784 Signed-off-by: James Stocks <jstocks@chef.io>
Hello,
With the release of v1.13.0, our test builds on Windows are failing.
Excerpt from AppVeyor build log
The text was updated successfully, but these errors were encountered: