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
A script similar to the one below will leak a gigabyte memory per minute (due to tight loop of course). The leak appears to be caused by the fact of not releasing the key after it has been added to the dictionary which adds its own reference.
It is worth noting that the function has an unrelated logical flaw - it currently cannot handle duplicate instance names (https://learn.microsoft.com/en-us/windows/win32/perfctrs/handling-duplicate-instance-names). Not sure how it should be addressed. Either creating a duplicate function (waste) or enhancing the function to have a value in the dictionary as formatted value or a list, when there is a duplicate instance (but it may break existing usage). On the other hand, due to very significant memory leak without prior reporting perhaps the function is not actively used and can be modified.
pywin32/win32/src/win32pdhmodule.cpp
Line 677 in 3a3e0e9
A script similar to the one below will leak a gigabyte memory per minute (due to tight loop of course). The leak appears to be caused by the fact of not releasing the key after it has been added to the dictionary which adds its own reference.
pywin32/win32/src/win32pdhmodule.cpp
Line 722 in 3a3e0e9
It is worth noting that the function has an unrelated logical flaw - it currently cannot handle duplicate instance names (https://learn.microsoft.com/en-us/windows/win32/perfctrs/handling-duplicate-instance-names). Not sure how it should be addressed. Either creating a duplicate function (waste) or enhancing the function to have a value in the dictionary as formatted value or a list, when there is a duplicate instance (but it may break existing usage). On the other hand, due to very significant memory leak without prior reporting perhaps the function is not actively used and can be modified.
The text was updated successfully, but these errors were encountered: