https://www.infopathdev.com:443/forums/40.aspxFor browser form specific questionsenCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/24822.aspxFri, 30 Nov 2007 15:58:51 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:24822jlehew0https://www.infopathdev.com:443/forums/thread/24822.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=40&PostID=24822<p>We modified the massive core.js file to not instanciate the HTML editor until you click into the field.&nbsp; This greatly reduced the leak when opening the form and viewing the information.&nbsp; And when the form is closed, as long as the user didn&#39;t click into a field, the memory that was used is garbage collected and can be used again.&nbsp; </p> <p>If InfoPath didn&#39;t put the editor inside an IFrame it would have worked.&nbsp; The IFrame is pinning down the memory for some reason.&nbsp; This is not a total solution but when the system consumes 100MB every time the user clicks on something, anything helps.&nbsp; </p> <p>John</p>https://www.infopathdev.com:443/forums/thread/24315.aspxFri, 09 Nov 2007 22:47:49 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:24315jlehew0https://www.infopathdev.com:443/forums/thread/24315.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=40&PostID=24315<p>We are having a significant memory leak on browser based forms that use the Rich Text boxes with IE7.&nbsp; When we switch views it adds 35K of memory to the iexplorer.exe process and this memory is still pinned even after closing the form popup window.&nbsp; As the users use our system and run close to the memory limits the window/Form Services either crashes completely, takes the CPU utilization to 100%, says it ran out of memory, or gives a few other random errors.&nbsp; The end result is our users cannot save and lose their data they were entering.&nbsp; This problem is easy to duplicate and we opened up a case with Microsoft who also verified and duplicated the problem. </p> <p>MS said the fix will take time because it happens within the core .dll modules of IE7.&nbsp; I don&#39;t understand why a memory leak that can be easily duplicated at MS is not a priority.&nbsp; It is not like we have another option for a multiline textbox.&nbsp; The only other option doesn&#39;t support paragraphs so everything that is typed in shows up as one big paragraph.&nbsp; Or we could switch to Rich Client based forms instead of the Browser based forms, but that would require architecture changes to our system.</p> <p>If anyone has a suggestion let me know.&nbsp; We had to upgrade all PCs to 2GB of memory (cost of $35,000) to minimize this issue but users who do not restart their IE7 often still run into this issue.</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p>