Skip to content

Conversation

@MartinDelille
Copy link
Contributor

PR checklist

  • Read the contribution guidelines.
  • Ran the shell script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in .\bin\windows\. If contributing template-only or documentation-only changes which will change sample output, be sure to build the project first.
  • Filed the PR against the correct branch: master, 4.1.x, 5.0.x. Default: master.
  • Copied the technical committee to review the pull request if your PR is targeting a particular programming language.

Description of the PR

I found a memory leak thanks to valgrind. Eventually it could be possible to use valgrind in the CI to make sure that the change doesn't bring more memory leaks.

@ravinikam @stkrwork @etherealjoy @muttleyxd

@wing328
Copy link
Member

wing328 commented Aug 16, 2019

Eventually it could be possible to use valgrind in the CI to make sure that the change doesn't bring more memory leaks.

Totally agreed. We should use it in all auto-generated C++ code.

@etherealjoy
Copy link
Contributor

Yeah, I missed it when adding the timeout feature. :(

@MartinDelille MartinDelille mentioned this pull request Aug 16, 2019
4 tasks
@MartinDelille
Copy link
Contributor Author

@wing328 I'll add it in another PR.

@etherealjoy etherealjoy added this to the 4.1.1 milestone Aug 17, 2019
@etherealjoy etherealjoy merged commit 024f468 into OpenAPITools:master Aug 17, 2019
@MartinDelille MartinDelille deleted the fix-memory-leak branch August 19, 2019 06:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants