-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Request transform causes an out-of-memory panic #1122
Comments
I wouldn't call this a leak. A leak is something that slowly fills up memory and never frees it. This crashes the gateway in mere seconds (at least on my laptop), as memory fills up incredibly fast. @ilijabojanovic have you tried stable? what happens there? |
@mvdan issue is not visible on current stable. When i trigger call to transformed endpoint, gateway starts to eat memory and crash when consumes all memory. |
cool, thanks |
This seems to be a bug in the |
This was a crash in the mxj library concerning invalid input from a reader, as it would not properly error and stop. We did not hit this before in 2.3.x as we used a []byte, not an io.Reader. The upstream issue is clbanning/mxj#38, fixed back in February. Add a regression test and bump the vendored version. Fixes #1122.
Branch: Master
rev: d83299a
Reproduction steps:
Here is testing api definition:
Trigger GET call to /ip endpoint
Gateway will crash without panic. In log i just have this:
The text was updated successfully, but these errors were encountered: