gh-143807: Fix JIT executor overflow caused by large backoff values#143812
gh-143807: Fix JIT executor overflow caused by large backoff values#143812VanshAgarwal24036 wants to merge 1 commit intopython:mainfrom
Conversation
7ba983b to
ee2f621
Compare
|
Is the change to |
|
Sorry but this fix doesn't seem right. The problem isn't with the warmup/backoff values. |
|
Thanks for the clarification. That makes sense — I see now that reducing the backoff values only masks the issue rather than addressing the underlying executor growth problem. I’ll take another look at how executors are tracked and bounded in get_index_for_executor to understand the real root cause. Appreciate the feedback. |
|
@VanshAgarwal24036 if you're using an LLM to wholesale reply me, please look at our generative AI policy https://devguide.python.org/getting-started/generative-ai/ It's not acceptable to use genAI to wholly create a PR or reply comments. It's perfectly fine if you're using it to assist you. Please try to understand the code or comment at least after using the LLM. |
This PR fixes a JIT crash where executor table size could exceed
MAX_EXECUTORS_SIZE due to excessively large initial backoff values.
Reducing the initial values for backward jumps and side exits keeps
executor growth bounded while preserving existing cooldown and tracing
heuristics.
Fixes gh-143807.
📚 Documentation preview 📚: https://cpython-previews--143812.org.readthedocs.build/