simonb65
Alibre Super User
I've just opened a mid-size assembly that I created in V24. The first thing I notice is that just panning, rotating and zooming around the model soon gets V25 hung up for 5-10 seconds and becomes very laggy. The hang up is so long that I have time to open task manager, looks at the processes, and get a 'snip' capture of the Alibre process info ...
Resources after much panning, rotating and zooming around the model ...
This never used to be an issue in v24. By comparison, v24 was way better from a responsiveness perspective. I'm not sure what you folks at Alibre have done in v25, but it's not a step in the right direction. Hopefully you have already seen this from other users and are on the case, but as it stands, I maybe reverting back to v24 to work on this project, because v25 is not helping me get work done as quick.
Anyone else seen a change in v24 to v25 performance?
Anyone wondering why 2 Alibre processes are shown, it's just the Home Window and Assembly Workspaces, so that's very normal and expected ...
EDIT : Interestingly, closing and restarting Alibre and the memory usage is much lower, still laggy, but not as bad (still no where near as good as v24 though). Is there still a major memory leak somewhere? ...
Resources immediately after a restart ...
EDIT #2 : Close the assembly workspace (and back to the Home Window), then open the assembly again ...
Close the assembly workspace again ...
Open the assembly ...
Close the assembly ...
@Max, Not sure if Alibre uses the .NET Garbage Collector internally or good 'ole fashioned Malloc()/Free() or create/delete, but something isn't getting emptied or Free'd when a workspace is closed! Maybe you can pass this on to dev please. I would have raised a ticket, but you can't express issues as easy and flexible as you can on a forum post.
30 minutes later after no Alibre activity and no assembly open (just the Home Window), and memory is still being tied up and not released ...
Resources after much panning, rotating and zooming around the model ...
This never used to be an issue in v24. By comparison, v24 was way better from a responsiveness perspective. I'm not sure what you folks at Alibre have done in v25, but it's not a step in the right direction. Hopefully you have already seen this from other users and are on the case, but as it stands, I maybe reverting back to v24 to work on this project, because v25 is not helping me get work done as quick.
Anyone else seen a change in v24 to v25 performance?
Anyone wondering why 2 Alibre processes are shown, it's just the Home Window and Assembly Workspaces, so that's very normal and expected ...
EDIT : Interestingly, closing and restarting Alibre and the memory usage is much lower, still laggy, but not as bad (still no where near as good as v24 though). Is there still a major memory leak somewhere? ...
Resources immediately after a restart ...
EDIT #2 : Close the assembly workspace (and back to the Home Window), then open the assembly again ...
Close the assembly workspace again ...
Open the assembly ...
Close the assembly ...
@Max, Not sure if Alibre uses the .NET Garbage Collector internally or good 'ole fashioned Malloc()/Free() or create/delete, but something isn't getting emptied or Free'd when a workspace is closed! Maybe you can pass this on to dev please. I would have raised a ticket, but you can't express issues as easy and flexible as you can on a forum post.
30 minutes later after no Alibre activity and no assembly open (just the Home Window), and memory is still being tied up and not released ...
Last edited: