# Stack probe puzzle

**URL:** <https://ziggit.dev/t/stack-probe-puzzle/10291>\
**Category:** Help\
**Tags:** memory-management\
**Created:** [May 28, 2025, 12:53pm UTC](https://ziggit.dev/t/stack-probe-puzzle/10291 "2025-05-28T12:53:02Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![matklad](https://ziggit.dev/user_avatar/ziggit.dev/matklad/32/2462_2.png) [@matklad](https://ziggit.dev/u/matklad)\
**Post date:** [May 30, 2025, 1:48pm UTC](https://ziggit.dev/t/stack-probe-puzzle/10291/2 "2025-05-30T13:48:13Z")

</div>

To preserve my sanity, I had to seal the rabbit hole:

 ![Kola Superdeep Borehole](https://ziggit.dev/uploads/default/original/2X/5/5fe0ceb8f12d0a1e266379f7e853ef0e43302681.jpeg)

> <https://github.com/tigerbeetle/tigerbeetle/pull/2999>
>
> Two changes here:
> 
> \* Set stack size for vopr and fuzz to 4\*MiB. Zig's default …stack size is
> 16\*MiB, but we want to make sure that we have ample free space. Given
> that we don't have a billion of dependencies, and that recursion is
> banned by TigerStyle, our stack size should be pretty shallow.
> 
> \* Eagerly fault-in the stack on startup for fuzzers, to, ahem, scare out
> the ghosts out of our CFO machines:
> https://ziggit.dev/t/stack-probe-puzzle/10291/1
> 
> This \_is\_ a work-around, but, based on the fact that it \_only\_ affects
> forest\_fuzz which does a lot of allocation and de-allocation, I do
> think there isn't any issue with our code, and, given that the root
> cause hasn't reveal itself after 3 days of investigation, it seems
> better to just table this for now.

I couldn’t bring myself to deleting the original core dump file. It will be waiting for the next foolish adventurer.

[https://github.com/matklad/repros/releases/download/artifacts/core.zst](https://github.com/matklad/repros/releases/download/artifacts/core.zst)

---

_[View the full topic](https://ziggit.dev/t/stack-probe-puzzle/10291)._