---
title: "Discussion on \"The Rust binding compiled fine. then it started segfaulting in prod\" | Hashnode"
description: "Discussion on \"The Rust binding compiled fine. then it started segfaulting in prod\". My \"safe\" Rust code was double-freeing a C object in production. The cause was a derived Clone on a libvips GObject handle. Here is the fix."
url: "https://hashnode.com/posts/the-rust-binding-compiled-fine-then-it-started-segfaulting-in-prod/6a2a6e46a7ab4a31949f01f6"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The Rust binding compiled fine. then it started segfaulting in prod](https://convertifydevblog.hashnode.dev/the-rust-binding-compiled-fine-then-it-started-segfaulting-in-prod?utm_source=hashnode&utm_medium=feed)

My "safe" Rust code was double-freeing a C object in production. The cause was a derived Clone on a libvips GObject handle. Here is the fix.

Jun 11 · 5 min read · convertifydevblog.hashnode.dev  
Read the article

-   [#rust](https://hashnode.com/tag/rust)
-   [#webdev](https://hashnode.com/tag/webdev)
-   [#seo](https://hashnode.com/tag/seo)
-   [#developer](https://hashnode.com/tag/developer)
-   [#ffi](https://hashnode.com/tag/ffi)
-   [#debugging](https://hashnode.com/tag/debugging)

## Written by

[Serhii Kalyna](https://hashnode.com/@serhiikalyna)

@serhiikalyna · Kyiv, Ukraine

  
[View profile](https://hashnode.com/@serhiikalyna)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
