Open mallechilie opened 9 months ago
I'm seeing this after about 220 iterations where the helper process grows to about 2.75GB while executing request that is processing pagenated elements of a list (list of target IDs, when queried may have paged results). This is repeatable. Additionally, I'm left with a Runner tab that needs to be force closed on restart. (I'm pulling from an Okta API, and collating results in variables.)
My prereqeust script pulls from a variable to set a query ID, and optionally the continued pagination of results. My test script aggregates the results.
I'm running on MacOS 14.3.1, Postman (Desktop) version 10.24.3, both are up to date as of this writing.
Is there an existing issue for this?
Describe the Issue
When doing a manual run with enough requests (50+), postman crashes.
This seems to be a memory issue: There's a clear rise in memory usage until the crash happens.
This crash results in the following issue.
Steps To Reproduce
Screenshots or Videos
No response
Operating System
Windows
Postman Version
10.12.11
Postman Platform
Postman App
User Account Type
Signed In User
Additional Context?
No response