This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kj
Recipients BTaskaya, belopolsky, benjamin.peterson, eric.snow, gregory.p.smith, kj, meador.inge, miss-islington, pablogsal, ppperry, terry.reedy
Date 2021-06-05.17:36:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1622914599.99.0.453927762083.issue11105@roundup.psfhosted.org>
In-reply-to
Content
The newly added test ``test_recursion_direct`` seems to trigger a stack overflow on windows in debug mode instead of a RecursionError. Release mode isn't affected and the test passes there.

One of the buildbots reflects this too: https://buildbot.python.org/all/#/builders/146/builds/337/steps/4/logs/stdio

I can avoid the crash by lowering the recursion limit in Python from 1000 to 500. The stack size for a window build is currently set to 2MB, which is usually lesser than *nix 8MB. So I think an easy solution is to increase the stack size for windows builds.

I'm guessing release builds aren't affected because some of the Py_EnterRecursiveCall helper functions are probably inlined and thus use less of the stack.

Opinions are greatly appreciated.
History
Date User Action Args
2021-06-05 17:36:40kjsetrecipients: + kj, terry.reedy, gregory.p.smith, belopolsky, benjamin.peterson, meador.inge, eric.snow, ppperry, pablogsal, miss-islington, BTaskaya
2021-06-05 17:36:39kjsetmessageid: <1622914599.99.0.453927762083.issue11105@roundup.psfhosted.org>
2021-06-05 17:36:39kjlinkissue11105 messages
2021-06-05 17:36:39kjcreate