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 pablogsal
Recipients dino.viehland, pablogsal
Date 2019-05-08.15:40:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1557330055.15.0.678827851719.issue36851@roundup.psfhosted.org>
In-reply-to
Content
When evaluating a frame object, it is possible to exit the execution with some variables in the stack. The frame deallocator (frame_dealloc) only cleans the stack if f_stacktop is not NULL, but this only happens for generators and when trace functions are set. The eval loop does this cleanup already if an exception is being raised, but not if a RETURN_VALUE is set.

In the PyconUS sprints, Dino and I have been working on this and we have decided that the cleanest approach is shared the same goto label with the path for exception handling, effectively cleaning up
History
Date User Action Args
2019-05-08 15:40:55pablogsalsetrecipients: + pablogsal, dino.viehland
2019-05-08 15:40:55pablogsalsetmessageid: <1557330055.15.0.678827851719.issue36851@roundup.psfhosted.org>
2019-05-08 15:40:55pablogsallinkissue36851 messages
2019-05-08 15:40:54pablogsalcreate