Bug: BatchExecutor exhibits a memory leak leading to degraded performance over time

[Jaydbrown]

Description

During extensive QA testing, we identified a critical flaw where the BatchExecutor component exhibits a memory leak leading to degraded performance over time.

This results in a poor developer experience for anyone consuming our SDK.

Steps to Reproduce

1. Initialize the BatchExecutor module in a standard production environment.
2. Trigger the specific edge case (e.g., rapid state changes or malformed input).
3. Observe the system state. Notice that it exhibits a memory leak leading to degraded performance over time instead of returning the expected output or gracefully handling the error.

Technical Analysis

The root cause appears to be a missing boundary check or improper lifecycle management within the core logic of BatchExecutor. When the asynchronous operation resolves, the state may have already mutated, leading to this bug.

Requirements for Fix

• Add explicit boundary and null checks before processing the payload.
• Ensure all asynchronous callbacks are properly cleaned up.
• Write a comprehensive regression test that simulates this exact failure mode to prevent future regressions.

Bounty Tier: $150 (Critical Bug)

[jesutobaadedejidev]

I would like to work on this issue. Do assign it to me.

[somotochukwu-dev]

@somotochukwu-dev has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Please assign this issue to me
Thanks

ℹ️ Repo Maintainers: To accept this application, review their application or assign @somotochukwu-dev to this issue.

[Syringe7]

@Syringe7 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I would love to work on this issues

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Syringe7 to this issue.

[drips-wave]

Congratulations, @Syringe7! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Syringe7: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

Congratulations, @Syringe7! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Syringe7: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊