IronLanguages / IronLanguages/ironpython3
StackOverflowException even when MaxRecursion is set
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 316
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 1
Description
It seems like we're using up the .NET runtime stack quite quickly which limits the usefulness of the MaxRecursion limit. For example, even when running the code from https://github.com/IronLanguages/ironpython3/issues/1610 with a MaxRecursion limit we can end up with a stack overflow if the value is too high, but if we set it too low, then we get a RecursionError on import...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior described in issue 1610 with different MaxRecursion values. Investigate how recursion limits interact with the .NET runtime stack and import-time recursion. Done means avoiding an unintended StackOverflowException while preserving the expected RecursionError behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100