# Who’s at Fault: Tracking Down Segfaults in Production | Blog

**URL:** https://meta.discourse.org/t/who-s-at-fault-tracking-down-segfaults-in-production-blog/205264
**Category:** Blog
**Created:** [October 5, 2021, 2:11pm UTC](https://meta.discourse.org/t/who-s-at-fault-tracking-down-segfaults-in-production-blog/205264 "2021-10-05T14:11:57Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![fitzy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fitzy/32/192549_2.png) [@fitzy](https://meta.discourse.org/u/fitzy)
#### Post date: [October 5, 2021, 2:11pm UTC](https://meta.discourse.org/t/who-s-at-fault-tracking-down-segfaults-in-production-blog/205264/1 "2021-10-05T14:11:57Z")

</div>

Within complex applications and hosting environments, segfaults can manifest themselves in a myriad of weird and wonderful symptoms. For Discourse the application, this may be a notification email failing to send, or an uploaded image failing to be optimized, or many other not-very-noticeable problems.

* * *
This is a companion discussion topic for the original entry at [https://blog.discourse.org/2021/10/tracking-down-segfaults-in-production](https://blog.discourse.org/2021/10/tracking-down-segfaults-in-production)