-
Notifications
You must be signed in to change notification settings - Fork 46
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
Memory Leak #21
Comments
Hello @Marcello-debug Please refer to #20 (comment) Thanks! |
Thank you @sstevan for your fast and precise response. Marcello |
@Marcello-debug have tried bugfix branch without adding sleep time? If you are putting measurements into sending queue faster than the actual reporting rate this "memory leak" is going to appear. So, if you are having a delay of 20ms before putting measurement into sending queue you are actually creating 50 measurements per second and your reporting rate is 30 measurements per second. This means for each second you will put 20 measurements extra in a queue which will not be sent for that exact second. That is why putting sleep delay the same as (near) reporting rate will give you better memory usage. |
Thanks again. Marcello Code:
|
Hey @Marcello-debug I understand your issue much better now. The issue is caused by stopping the PDC. At this point, there is no elegant way of letting know the feed script (that is generating measurements) that generating should stop. We will add this to our roadmap as a handy feature. However, what you can do is to try to disconnect the PDC (close connection) and check |
Thank you again for your reply.
Attached you can find my code if you want to test the issues yourself. Regards Marcello |
Hello!
I tried randomPMU server connected with tinyPDC client. I experienced a memory leak (quite visible also from task manager) that brings to a MemoryError.
O.S. is win7 SP1. Synchrophasor version 1.0.0a0.
Thank you in advance for your help.
Regards
Marcello
The text was updated successfully, but these errors were encountered: