Christian von Arnim

If I'm not mistaken, you should only need the struct/enum, as the UA_Datatype Definition is already known from the nodeset importer. Use `UA_Server_findDataType` to get the correct DataType definition. https://github.com/open62541/open62541/blob/d01f197153ca1cffecc3eb7b0d0027eec1ebd9e1/include/open62541/server.h#L1850-L1853

> 3. `UA_Server_findDataType` will be way slower than direct access to the `UA__TYPES` array... any possible improvements? In case you need these types often, just query them once and store...

No, it's just some local isolated testing.

https://github.com/umati/Dashboard-OPCUA-Client/pull/new/debug_IjtResultType This is my test script https://github.com/umati/Dashboard-OPCUA-Client/blob/e79574a08fe7c4f9bd9e0ffa15563984991da942/TestResultType.cpp

No, the client does not hanlde `GeneralModelChangeEvents` at the moment.

You once talk about a sequence of UA_new/UA_delete that cause a memory problem. Can you please share this with me. This valgrind issue is nearly impossible to debug, as it...

> ` ==24== 15,053 (16 direct, 15,037 indirect) bytes in 1 blocks are definitely lost in loss record 60 of 61` This is not related to ResultManagement, as this message...

Is there any open62541-based OPC UA server available? ``` Traceback (most recent call last): File "/home/lxam/UmatiClient_ResultManagement/Sample-Server/installDeps/share/open62541/tools/generate_datatypes.py", line 95, in parser.create_types() File "/home/lxam/UmatiClient_ResultManagement/Sample-Server/installDeps/share/open62541/tools/nodeset_compiler/type_parser.py", line 384, in create_types self.parse_types() File "/home/lxam/UmatiClient_ResultManagement/Sample-Server/installDeps/share/open62541/tools/nodeset_compiler/type_parser.py", line...

This application isolates the problem: https://github.com/umati/Dashboard-OPCUA-Client/blob/e79574a08fe7c4f9bd9e0ffa15563984991da942/TestResultType.cpp (Branch https://github.com/umati/Dashboard-OPCUA-Client/pull/new/debug_IjtResultType)

When the growth is bigger on the VM, this is propably related to the number of client requests/ subscriptions. Might be also caused by the copy mechanism of values which...