<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Free memory after Function call in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/free-memory-after-function-call/m-p/5202077#M1203502</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ivo,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sounds like a "enldess transaction" pattern.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Take multiple memory snapshots (OK-CODE /HMUSA) in your application and compare&lt;/P&gt;&lt;P&gt;these in transaction S_MEMORY_INSPECTOR in order to find out if there is a memory &lt;/P&gt;&lt;P&gt;leak. The comparison will show you where memory growth comes from... maybe this gives&lt;/P&gt;&lt;P&gt;you an idea what could be deleted between the steps of your endless transaction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hermann&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 24 Feb 2009 09:31:04 GMT</pubDate>
    <dc:creator>HermannGahm</dc:creator>
    <dc:date>2009-02-24T09:31:04Z</dc:date>
    <item>
      <title>Free memory after Function call</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/free-memory-after-function-call/m-p/5202075#M1203500</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a possibility to free the memory after a call to a function.&lt;/P&gt;&lt;P&gt;The call is only used for display, not to get data.&lt;/P&gt;&lt;P&gt;(For example - CALL FUNCTION 'FKK_BUPA_DISPLAY')&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our z-transaction delivers a way of navigating through different ISU objects (coming from an ALV list)&lt;/P&gt;&lt;P&gt;The user first selects a case from this list and then he receives the details. From the details screen we then call these standard function to display the ISU objects.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During the day memory usage is getting build up and it's only released when the user leaves our z-transaction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ideally the memory should be released when the user returns to the list and not at the end of the day when he leaves the transaction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've tried with FREE MEMORY but this doesn't help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ivo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Feb 2009 07:49:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/free-memory-after-function-call/m-p/5202075#M1203500</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-02-24T07:49:49Z</dc:date>
    </item>
    <item>
      <title>Re: Free memory after Function call</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/free-memory-after-function-call/m-p/5202076#M1203501</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ivo&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One thing you could try is to create a zFM in the same Function Group as of your FM. Now in this FM write FREE MEMORY statement or FREE all objects which might be causing the memory build up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pushpraj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Feb 2009 08:11:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/free-memory-after-function-call/m-p/5202076#M1203501</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-02-24T08:11:20Z</dc:date>
    </item>
    <item>
      <title>Re: Free memory after Function call</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/free-memory-after-function-call/m-p/5202077#M1203502</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ivo,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sounds like a "enldess transaction" pattern.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Take multiple memory snapshots (OK-CODE /HMUSA) in your application and compare&lt;/P&gt;&lt;P&gt;these in transaction S_MEMORY_INSPECTOR in order to find out if there is a memory &lt;/P&gt;&lt;P&gt;leak. The comparison will show you where memory growth comes from... maybe this gives&lt;/P&gt;&lt;P&gt;you an idea what could be deleted between the steps of your endless transaction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hermann&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Feb 2009 09:31:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/free-memory-after-function-call/m-p/5202077#M1203502</guid>
      <dc:creator>HermannGahm</dc:creator>
      <dc:date>2009-02-24T09:31:04Z</dc:date>
    </item>
    <item>
      <title>Re: Free memory after Function call</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/free-memory-after-function-call/m-p/5202078#M1203503</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you tried SUBMIT AND RETURN to encapsulate your function calls?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Feb 2009 16:57:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/free-memory-after-function-call/m-p/5202078#M1203503</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-02-27T16:57:14Z</dc:date>
    </item>
  </channel>
</rss>

