Alpha Video Training
Results 1 to 10 of 10

Thread: Build 6232-5386 Memory Leak - How to fix

  1. #1
    Member
    Real Name
    Scott Moore
    Join Date
    Oct 2010
    Posts
    255

    Default Build 6232-5386 Memory Leak - How to fix

    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

  2. #2
    "Certified" Alphaholic kkfin's Avatar
    Real Name
    Kenneth
    Join Date
    Dec 2006
    Location
    EU
    Posts
    1,556

    Default Re: Build 6232-5386 Memory Leak - How to fix

    Can you really fix the memory leak?

    In my understanding just a pure html page is enough for WAS and memory will go up in long term (few days).


    Kenneth

  3. #3
    Member
    Real Name
    Scott Moore
    Join Date
    Oct 2010
    Posts
    255

    Default Re: Build 6232-5386 Memory Leak - How to fix

    Hi Kenneth,

    Good point, I should have clarified a bit more.

    There is still a very slow memory creep over the day that requires a restart each night or every couple of days depending on usage (I use always up). But this has always been the case and in my view the nightly restart is not an issue. But the memory leak I encountered was jumping by hundreds of MB per hour and would have required multiple restarts throughout the day, so not an acceptable situation.

    Cheers,

    Scott

  4. #4
    "Certified" Alphaholic kkfin's Avatar
    Real Name
    Kenneth
    Join Date
    Dec 2006
    Location
    EU
    Posts
    1,556

    Default Re: Build 6232-5386 Memory Leak - How to fix

    Quote Originally Posted by ssmoore1 View Post
    Hi Kenneth,

    Good point, I should have clarified a bit more.

    There is still a very slow memory creep over the day that requires a restart each night or every couple of days depending on usage (I use always up). But this has always been the case and in my view the nightly restart is not an issue. But the memory leak I encountered was jumping by hundreds of MB per hour and would have required multiple restarts throughout the day, so not an acceptable situation.

    Cheers,

    Scott
    In the end the memory leak will end to the fact that the server is unresponsive.
    So nightly restart is de facto but it should not be.

    Kenneth

  5. #5
    Volunteer Moderator Steve Workings's Avatar
    Real Name
    Steve Workings
    Join Date
    Apr 2000
    Location
    The Dreaded Chair
    Posts
    5,619

    Default Re: Build 6232-5386 Memory Leak - How to fix

    Thank you for this Scott. I finally had a chance to do this yesterday and watch memory usage today. Definitely did the job, and so far no new problems that may be unintended from the bulk operation.
    -Steve


  6. #6
    "Certified" Alphaholic iRadiate's Avatar
    Real Name
    Stephen
    Join Date
    Jan 2011
    Location
    London, ON, Canada
    Posts
    1,665

    Default Re: Build 6232-5386 Memory Leak - How to fix

    I tried this Bulk Update and got a file copy error on about 95% of my 179 components.
    The really annoying part is that I had to click OK to acknowledge every single error that popped up.

    BulkUpdateError.png

    In my case, I have no idea what, if anything this bulk operation did behind the scenes.
    Alpha Anywhere v12.4.6.1.5 Build 6315-5397 IIS v10.0 on Windows Server 2019 Std in Hyper-V

  7. #7
    Volunteer Moderator Steve Workings's Avatar
    Real Name
    Steve Workings
    Join Date
    Apr 2000
    Location
    The Dreaded Chair
    Posts
    5,619

    Default Re: Build 6232-5386 Memory Leak - How to fix

    Did the last edit date change in your UX components? All of mine updated to the date/time I ran the update.
    -Steve


  8. #8
    "Certified" Alphaholic iRadiate's Avatar
    Real Name
    Stephen
    Join Date
    Jan 2011
    Location
    London, ON, Canada
    Posts
    1,665

    Default Re: Build 6232-5386 Memory Leak - How to fix

    Quote Originally Posted by Steve Workings View Post
    Did the last edit date change in your UX components? All of mine updated to the date/time I ran the update.
    No, looks like they did not update Steve.
    Alpha Anywhere v12.4.6.1.5 Build 6315-5397 IIS v10.0 on Windows Server 2019 Std in Hyper-V

  9. #9
    Volunteer Moderator Steve Workings's Avatar
    Real Name
    Steve Workings
    Join Date
    Apr 2000
    Location
    The Dreaded Chair
    Posts
    5,619

    Default Re: Build 6232-5386 Memory Leak - How to fix

    Well, no one's an expert on this point. I did this using build 6232_5386. If you are earlier than this, consider updating and trying again?

    Send a bug report with a single UX in a workspace that behaves this way.

    I'll be glad to try running an update on that as well if you want to send it to me. steve@workings.com
    -Steve


  10. #10
    "Certified" Alphaholic iRadiate's Avatar
    Real Name
    Stephen
    Join Date
    Jan 2011
    Location
    London, ON, Canada
    Posts
    1,665

    Default Re: Build 6232-5386 Memory Leak - How to fix

    Yes, I was on Build 6232_5386 when this didn't work. I always have the build that I'm running on in my signature.

    So, I just updated to today's Official release Build 6315_5397, re-ran the bulk update and now it ran fine without any errors.
    The timestamp on all 179 of my UX components now show the date/time I ran the bulk update.
    Last edited by iRadiate; Yesterday at 12:11 PM. Reason: typo
    Alpha Anywhere v12.4.6.1.5 Build 6315-5397 IIS v10.0 on Windows Server 2019 Std in Hyper-V

Similar Threads

  1. Memory Leak with .NET
    By dparker in forum Application Server Version 11 - Web/Browser Applications
    Replies: 6
    Last Post: 05-01-2012, 08:32 PM
  2. memory leak?
    By martinwcole in forum Alpha Five Version 8
    Replies: 1
    Last Post: 08-24-2008, 11:59 AM
  3. Memory Leak ?
    By rsisson in forum Alpha Five Version 7
    Replies: 8
    Last Post: 04-03-2006, 03:57 PM
  4. Memory Leak?
    By Redshift in forum Alpha Five Version 7
    Replies: 12
    Last Post: 01-03-2006, 12:01 PM
  5. memory leak in A5 build 1553_2044?
    By Hansolo in forum Web Application Server v6
    Replies: 0
    Last Post: 03-17-2005, 10:53 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •