Hi AdrianR,
No problem! I'll do my best to address your follow-up questions:
1. Some memory does get left behind when a form is closed and isn't always entirely freed up by standard garbage collection. This is something we are targeting for Update Rollup 15, however the amount of memory that is left behind can be significantly increased by org-specific customizations. Therefore, it's possible that any enhancements made in future Dynamics CRM patches will not have the same impact across all environments. My recommendation would be to make sure that any data that is being pinned or event handlers that are being called by custom code are properly disposed of.
2. I have seen certain scenarios where this can happen, and I believe this largely depends on how you're opening the forms and how many forms you have open at a given time. If you close the open CRM forms, the client should adjust the number of processes and their utilization accordingly.
3. If you enable client-side tracing through Diagnostics (Advanced Troubleshooting tab) with the Critical Update installed, there will be a new WebFormsHost log file placed in the %USERPROFILE%\AppData\Local\Microsoft\MSCRM\Traces folder. The callstacks in this log file will indicate the client's Virtual Memory calculations and the results of the new CheckMemoryThreshold method. This method returns a "Memory Threshold Hit" message when it reaches one of the configured thresholds. Whether the client moves to the second process or creates a new one will be determined by the scenarios outlined in my previous post.
4. I have done a lot of stress testing myself, but have not encountered any memory-related error messages after opening such a small number of forms. If you can reproduce this behavior, I would encourage you to open a support case so that it can be investigated more thoroughly.
↧
Forum Post: RE: Memory Management issuein CRM Client for Outlook UR11 Critical Update
↧