Hi Everyone,
I am just passing this along, Alpha might have a different opinion on this but it worked for me. The is for the classic application server, not IIS.
The latest release 6232-5386 has a bug fix for a memory leak:
Application Server - Memory Leak - Fixed a memory lead the property_recurse_assign() function. Since this function is used in both the UX and Grid components, web applications that used these components could see server memory increasing over time.
However, when I installed the latest release today and turned it on the memory leak problem was still there. My server went up 400 mb in memory in about 90 minutes. So I took one extra step and ran the bulk operation below:
UX Component - Bulk Operation - Starting with Build 5982, an internal change was made to the internal stored format for UX Components. While no change is needed on your part to run UX components build before 5982 with build 5982 or higher, you can optimize performance of these older UX components by editing them and resaving then with build 5982 or higher. When you resave the component, the internal stored format is updated to the newer format. You can also do this conversion using a Bulk Operation by selecting Edit, Bulk Operation, Update UX Components to V4.6.1. format.
It is recommended (but it is NOT required) that you perform this bulk operation and then republish your site.
After doing this bulk operation and republishing the components, the memory leak problem appears to be solved. So it appears that to fix this memory leak problem you do need to run the bulk operation to update your UX components. Maybe the memory leak bug fix only applies to the later V4.6.1 format, but that is just speculation on my part.
The bulk operation was very quick for 260 UX components so its easy to do.
Thanks,
Scott
I am just passing this along, Alpha might have a different opinion on this but it worked for me. The is for the classic application server, not IIS.
The latest release 6232-5386 has a bug fix for a memory leak:
Application Server - Memory Leak - Fixed a memory lead the property_recurse_assign() function. Since this function is used in both the UX and Grid components, web applications that used these components could see server memory increasing over time.
However, when I installed the latest release today and turned it on the memory leak problem was still there. My server went up 400 mb in memory in about 90 minutes. So I took one extra step and ran the bulk operation below:
UX Component - Bulk Operation - Starting with Build 5982, an internal change was made to the internal stored format for UX Components. While no change is needed on your part to run UX components build before 5982 with build 5982 or higher, you can optimize performance of these older UX components by editing them and resaving then with build 5982 or higher. When you resave the component, the internal stored format is updated to the newer format. You can also do this conversion using a Bulk Operation by selecting Edit, Bulk Operation, Update UX Components to V4.6.1. format.
It is recommended (but it is NOT required) that you perform this bulk operation and then republish your site.
After doing this bulk operation and republishing the components, the memory leak problem appears to be solved. So it appears that to fix this memory leak problem you do need to run the bulk operation to update your UX components. Maybe the memory leak bug fix only applies to the later V4.6.1 format, but that is just speculation on my part.
The bulk operation was very quick for 260 UX components so its easy to do.
Thanks,
Scott
Comment