Author vstinner
Recipients Arfrever, Mark.Shannon, amaury.forgeotdarc, asvetlov, benjamin.peterson, brett.cannon, dmalcolm, ilblackdragon, jcea, jkloth, larry, lemburg, mark.dickinson, python-dev, vstinner
Date 2013-07-02.15:45:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1372779901.78.0.750524501443.issue17206@psf.upfronthosting.co.za>
In-reply-to
Content
Jeremy: "stack for python_d.exe has been already up'ed to 2100000"

Indeed, but not recently (changeset 97361d917d22):

<< Issue 2286: bump up the stack size of the 64-bit debug python_d.exe to 2100000. The default value of 200000 causes a stack overflow at 1965 iterations of r_object() in marshal.c, 35 iterations before the 2000 limit enforced by MAX_MARSHAL_STACK_DEPTH. >>

Oh it looks like it was the same issue: "Stack overflow exception caused by test_marshal on Windows x64". See issue #2286.

Amaury wrote in this issue (in 2008, msg63540):
"Can you try to raise the stack size on x64 builds? If 2Mb is enough for 32bit, 4Mb should be good in your case."

Jeremy: "Therefore the reserve could be as large as needed to prevent stack overflows without impacting the actually memory footprint of the executable.  Maybe we should consider increasing the reserve to match that of Linux (8MB)?"

Ah ok, if the memory footprint is unchanged, yes please increase the arbitrary limit. I would suggest 8 MB.
History
Date User Action Args
2013-07-02 15:45:01vstinnersetrecipients: + vstinner, lemburg, brett.cannon, jcea, amaury.forgeotdarc, mark.dickinson, larry, benjamin.peterson, jkloth, Arfrever, asvetlov, dmalcolm, Mark.Shannon, python-dev, ilblackdragon
2013-07-02 15:45:01vstinnersetmessageid: <1372779901.78.0.750524501443.issue17206@psf.upfronthosting.co.za>
2013-07-02 15:45:01vstinnerlinkissue17206 messages
2013-07-02 15:45:01vstinnercreate