|
SFDiagram control used in the child component. It used to be bound based on the parent component cascading parameter. The first parent component request it took 5secs to bind(It's completely fine as it has some volume of data(approx. 150+ nodes) but in the 2nd parent request for the same dataset/cascading parameter it took 3mintues to create connectors without nodes and errored out as threading issue. There is no change in code/logic for first and 2nd parent request. I've attached the error screen shot for reference. |
We checked your attachment files , and tried to make sample like the same . But in our sample we didn’t find any issue as mentioned . Can you please share the runnable application so that it will easy for us to proceed further . Please find the sample which we checked for your further reference .
|
|
Apparently the memory has not released even after does Clear() on diagram object and observable collection objects. |
Can you please share the code snippet you are using while clearing , so that we can validate it from our end |
|
void ConstructDiagramModel()
{
// remove this lines
// NodeCollection.Clear();
//ConnectorCollection.Clear();
try
{
GenerateNodes();
GenerateConnectors();
}
catch (Exception e)
{
logger.LogError("StockDiagramHistory:ConstructDiagramModel()", e);
//toaster.Add(e.Message, MatToastType.Danger, "Message");
}
}
public void Refresh(List cpDataset)
{
if (enableSubSeqRender)
{
Diagram.Clear();
CPDataset = cpDataset;
if (CPDataset != null)
ConstructDiagramModel();
Diagram.DoLayout();
}
if (!enableSubSeqRender)
enableSubSeqRender = true;
}
|