-
Notifications
You must be signed in to change notification settings - Fork 454
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Out of Memory Error #232
Comments
hi from your stacktrace:
#231 will fix it. cc: @xthexder |
Please merge and release. |
Waiting on a quick +1 from another maintainer and for the contributor to agree to the CLA. Sorry for the long turnaround on this. |
This has been merged into master but I haven't had the chance to cut a release yet. Just got back from break so I should have time this week to cut a release. |
Thanks. |
We are consistently getting Out of Memory errors with Toxiproxy, with both the Docker image and the Windows executable. We are using version 2.1.3.
We've been creating a proxy for an AWS S3 bucket (i.e. bucketName.s3.amazonaws.com) and adding upstream and downstream latency toxics (with
--toxicity 0.05
). We then run a test that eventually uploads about 2000 small text files to S3. We're generally able to run a few of these tests before the server crashes. With the Windows server, we see the Toxiproxy process using up to ~9GB of available memory before crashing. Typically, the process will continue running for a few minutes after the tests complete before it crashes, but doesn't seem to free up any of the memory it's using before crashing.Stack trace from the Docker image:
The text was updated successfully, but these errors were encountered: