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 jkloth
Recipients Arfrever, Mark.Shannon, amaury.forgeotdarc, asvetlov, benjamin.peterson, brett.cannon, dmalcolm, ilblackdragon, jcea, jkloth, larry, lemburg, mark.dickinson, python-dev, vstinner
Date 2013-06-25.22:00:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1372197632.52.0.902454933651.issue17206@psf.upfronthosting.co.za>
In-reply-to
Content
Here are some results after a detailed investigation:

- in debug, each variable declaration in a block is allocated on the stack
- in debug, r_object() uses 1416 bytes of stack 
- in release, r_object() uses 512 bytes of stack
- default stack size is 1MB
- stack for python_d.exe has been already up'ed to 2100000

So it seems that the best option would be to increase the stack size used when linking (/STACK:).  I would suggest increasing it to 3MB using /STACK:3145728.
History
Date User Action Args
2013-06-25 22:00:32jklothsetrecipients: + jkloth, lemburg, brett.cannon, jcea, amaury.forgeotdarc, mark.dickinson, vstinner, larry, benjamin.peterson, Arfrever, asvetlov, dmalcolm, Mark.Shannon, python-dev, ilblackdragon
2013-06-25 22:00:32jklothsetmessageid: <1372197632.52.0.902454933651.issue17206@psf.upfronthosting.co.za>
2013-06-25 22:00:32jklothlinkissue17206 messages
2013-06-25 22:00:32jklothcreate