Assembly context no longer linked to the source

[ltomuta]

One of my top down designs has developed huge performance issues. It takes forever to open a component and even more to open the assembly.

To investigate the issue I thought I should export the assembly, upload it as a new instance and then play with that as a sandbox. But after upload, the assembly reports all external components as broken

So I opened one of the components and after chewing on it for a while Fusion presented me with a component with broken contexts:

I tried to fix them one by one but I don't really have any options

I don't even know to which component this was supposed to be linked to so I don't know what to open.
At least one of my components had an assembly context pointing to another design and I don't see that design exported with my assembly although it should be a dependency of it by way of subcomponent's context, right?

Part of attempting to solve the initial performance once idea is to nuke the the timelines in all these components and rebuild the assembly starting from base features. So at least for that this copy should be still usable. But for nothing else given the broken contexts.

Unless there is a way to fix them. Or a better way to export/copy the source design(s).

[ltomuta]

After deleting the contexts and the timeline apparently my part consists of 477400 threads and a several other features 🙂

[raymondxu]

Hi @ltomuta , 

Sorry for the problem. We are proactively working on a similar issue with too many threads. Even with broken context, can you share the dataset with us? If you want to just send to me, please feel free to send to raymond.xu@autodesk.com.

I think current workaround could be deleting these threads if you do not need them in direct modeling env. 

[LishuangLu]

Hi @ltomuta , Thanks for reporting and analyis on the cause of the issue! 
So this is a known issue due to the leak of threads feature cauing by some potential operations which is currently being investigated by the project team as Raymond said in above. 

We have improved the performance for several modeling operations caused by the large amount threads like expand browser, EIP, sketch and other modeling operations under EIP, which will be included by Fusion March release. It would be good that you can have a try when March release is available to you, and see it can benefit to your cases. 

In the meanwhile, currently the project team is invesitgating on how to avoid the thread leak and preventing the problem eventually.

Regards, 

-Lisa

[ltomuta]

I did just open my original design with the current insider build and although it took a looooot of computing I was able to fetch the latest version of the external components, compute all the contexts and save the design(s) with the latest version. The saving itself tool a lot of time too, especially uploading the assembly file.

There is still a lag on subsequent openings and closings of the design (no save) with the Home App stuck in this stage 

and Fusion becoming temporarily unresponsive. I find this surprising as the design is not really that complex and I can't imagine what kind of compute is still being done on it on closing. But at least I can work on it now so the main problem is gone.