Skip to main content
A
Anonymous
June 9, 2009
Answered

CF8.0.1 Hotfix 2 Fix Details

  • June 9, 2009
  • 2 replies
  • 1007 views

http://kb2.adobe.com/cps/403/kb403781.html has information on hotfix 2 and references a number of IDs.

Can anyone point us towards more information regarding the ID numbers referenced in the page above?

Particularly,

ID: 72641

Fix for memory leaks with CFCs stored in memory scopes. Note, this does not eliminate need for proper use of VAR scope in CFC methods.

I think I've been hitting problems related to this but I can't be certain without more detail.  Does Adobe have greater detail about these ID numbers publicly available?  I haven't been able to find any related documentation.

Thanks,

Bob Albright

    This topic has been closed for replies.
    Correct answer

    Bob,

    That was a bug we worked with Adobe on last summer.  I don't recall all of the issues surrounding it.  But, I found this description in one of my emails about what engineering found when they evaluated our issue:

    1. If a cfm creates a cfc and that cfc is kept in a long lasting scope like application/session, the entire object tree for the cfm request including the variables created in the cfm stays in the memory.

           

    2. If a cfc 'A' creates another cfc 'B' in a function, and 'B' is kept in a long lasting scope like application/session, A's data gets stuck in the memory. The reason is A's functionLocalScope gets added to the 'B' pageContext and is never removed. B keeps holding all the function local scope objects that was created in that function in A.

    2 replies

    A
    Anonymous
    June 19, 2009

    ?

    A
    Anonymous
    Correct answer
    June 19, 2009

    Bob,

    That was a bug we worked with Adobe on last summer.  I don't recall all of the issues surrounding it.  But, I found this description in one of my emails about what engineering found when they evaluated our issue:

    1. If a cfm creates a cfc and that cfc is kept in a long lasting scope like application/session, the entire object tree for the cfm request including the variables created in the cfm stays in the memory.

           

    2. If a cfc 'A' creates another cfc 'B' in a function, and 'B' is kept in a long lasting scope like application/session, A's data gets stuck in the memory. The reason is A's functionLocalScope gets added to the 'B' pageContext and is never removed. B keeps holding all the function local scope objects that was created in that function in A.

    A
    Anonymous
    June 19, 2009

    Interesting.  We do that all of the time in our application so that's good to know.

    Thanks for the reply.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices