-
Notifications
You must be signed in to change notification settings - Fork 3
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
test code for memory growing problem #1
base: master
Are you sure you want to change the base?
Conversation
Thanks for this. We can check the problem here at first.
It will help to setup the test environment, and will make the issue more clear. If you are in an emergency, you can use your forked and patch version from a rosinstall, everything will work fine. It would be good if we can write memory leak tests for the new version. When you get time it will be good if you can switch to use these branches to check it, and be ready for next version. |
Please also edit the author of these commit to a proper user. |
I found that it's not a problem of pros_schemas, so I left an issue https://github.com/marshmallow-code/marshmallow/issues/732 |
Ah good to know thanks. But it still means that users, on robots, care about memory usage details, and it would be good if we can find a way to check memory usage automatically during testing of pyros-msgs and pyros-schemas. Let me know if you have an idea or a piece of code that can be used to check memory usage, or reference cycle with pytest (using objgraph, or pympler, or something similar). pyros-dev/pyros-msgs#27 |
I added test code to show memory growing in pros_httpbin/nodes/leaktest.py and fixed_leaktest.py
we are in serious because we are using it in the field.
could you make a pyros_schemas 's devel branch first?