From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
06-13-2020 09:19 AM
All,
I found a reference leak when using python execution node. I am using LV 2020 SP1 and observed the leak in python 2.7 and python 3.8 (not officially supported but run wells in my application).
VI use: Example VI: PythonNode_AddTwoDoubles.vi (or any VI using python node).
Here is DETT logging for reference.
0 21:12:00.1225266 PythonNode_AddTwoDoubles.vi VI Start Execution 5 3
1 21:12:00.1225323 PythonNode_AddTwoDoubles.vi VI Call 5 3 subVI UID:0
2 21:12:00.1225366 ToPythonVersionString.vi VI Call 5 3 subVI UID:101
3 21:12:00.1225390 ToPythonVersionString.vi VI Return 5 3 subVI UID:101
4 21:12:00.1873769 GetExampleModulePath.vi VI Call 5 6 subVI UID:567
5 21:12:00.1873979 GetExampleModulePath.vi VI Return 5 6 subVI UID:567
6 21:12:00.1883626 PythonNode_AddTwoDoubles.vi VI Return 5 3 subVI UID:0
7 21:12:00.1883645 PythonNode_AddTwoDoubles.vi VI Stop Execution 5 3
8 21:12:00.2003264 PythonNode_AddTwoDoubles.vi Reference Leak 0 4 Unknown Leak : 0x8CF00000
Is this a true leak or we can safely ignore it?
06-15-2020 11:40 AM
Hard to tell. Perhaps that unsupported configuration you are running isn't running so well after all...
06-15-2020 04:33 PM
Thanks for your reply.
I was checking it with python 2.7 which is officially supported, and I saw the leak.
The DETT data I shared is using python 2.7.
06-15-2020 05:27 PM - edited 06-15-2020 05:27 PM
Hmmm, it would be tough to know if it is a "true" leak, as it would take quite a while to become noticeable. Maybe you could watch the memory in the VI Analyzer?