shushustorm Posted October 7, 2022 Share Posted October 7, 2022 Hey everyone! I ran into Designer showing the beach ball whenever I moved full screen focus to it. Looking into the activity monitor, it showed more and more increasing RAM usage by Designer. The file was getting somewhat complex, so I closed it and opened a very small file. The issue still showed up. Had to restart Designer and the complex file now works fast again. Not sure what caused it. Working on that same file, this didn't show up later anymore. Seems sporadic. Is there a known issue with Designer 1.10.4 getting memory leaks? This may not be the most current version. I am rarely updating in order to keep workflow stability. I searched for "memory leak" and didn't find this issue. Best wishes, Shu Quote Link to comment Share on other sites More sharing options...
Staff Lee_T Posted October 7, 2022 Staff Share Posted October 7, 2022 Hi shishustorm, You'd need to update your software and let us know if you are still having the issue. Functionally they are the same. It's worth noting that it's not a memory leak if you regain the memory back after closing the application, it's just the application using the available memory to keep performance. Your system may have beach balling due to lack of available memory for your project and paging to disk as a backup. Lee Quote Link to comment Share on other sites More sharing options...
GarryP Posted October 7, 2022 Share Posted October 7, 2022 In addition to what LeeThorpe said above, why are you making bug reports for 1.10.4? Any bug fixes would have to come out in a 1.10.6 update and so, if you are unwilling to update the software to the latest version, how would you expect to see the bug fixed for you? Lee_T 1 Quote Link to comment Share on other sites More sharing options...
shushustorm Posted October 8, 2022 Author Share Posted October 8, 2022 @LeeThorpe It's a very sporadic issue. Only ever showed up once. So I tried to get more info here whether there is a known scenario so I can avoid it. Also, the app used up more and more memory without changing anything within the file. Just by focusing and defocusing some times, the RAM usage went from a few hundred MB to above 1GB. @GarryP I'm not unwilling to update in general. But there's a time for it that makes sense and then there's a time for it when things run quite well and I don't need any features of newer versions - why would I risk breaking things by updating? That doesn't mean I don't appreciate bugs fixed in future versions down the road when I'm updating. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.