A critical bug has surfaced in one of the open-source tools that underpins our daily workflow, and I need a sharp set of eyes to track it down and squash it. The issue manifests as an unexpected crash during routine operations; logs point to a memory-handling fault, but the exact trigger remains elusive. Here’s the flow I have in mind: • Reproduce the bug on your local environment so we can confirm we’re seeing the same failure. • Trace the root cause—code review, breakpoints, anything that helps narrow the faulty module. • Craft a clean, well-commented patch that follows the project’s contribution guidelines. • Prove the fix: unit tests, regression checks, and a short write-up on how the solution eliminates the crash without side effects. • Submit a pull request (or equivalent) to the upstream repo and hand over a concise report outlining the changes. You’ll be working with standard open-source tooling: Git for version control, typical C/C++ build chains (the project uses CMake), and a small Python harness for automated testing. Familiarity with Valgrind or AddressSanitizer will help speed diagnosis, but you’re free to use the profilers you trust. Deliverables are considered complete once the patch is accepted upstream and all automated tests pass on CI. If anything feels unclear, let’s chat before you dive in—I’d rather confirm assumptions early than rework later.