You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for this repository, I can easily create an app with Flask .
I created a frameless window, When I slowly drag, sometimes the memory usage will continue to slowly increase and never decrease again, here is my code:
I can rule out the issue with my app as it is just a simple demo.
And you should have noticed that I did not use the built-in server. Because when I used the built-in server, I created 20 charts on the front-end and retrieved data from the backend every 5 minutes. The occupancy rate of the Python process would increase to around 900MB after running for a day, and this number continued to increase. When I used my own wgsi server, this problem would not occur.
Practicalities
NO I am willing to work on this issue myself.
NO I am prepared to support this issue financially.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Specification
Description
Thanks for this repository, I can easily create an app with Flask .
I created a frameless window, When I slowly drag, sometimes the memory usage will continue to slowly increase and never decrease again, here is my code:
I can rule out the issue with my app as it is just a simple demo.
And you should have noticed that I did not use the built-in server. Because when I used the built-in server, I created 20 charts on the front-end and retrieved data from the backend every 5 minutes. The occupancy rate of the Python process would increase to around 900MB after running for a day, and this number continued to increase. When I used my own wgsi server, this problem would not occur.
Practicalities
NO I am willing to work on this issue myself.
NO I am prepared to support this issue financially.
The text was updated successfully, but these errors were encountered: