Although the timeframe suggests the problem may be deeper, you still should make sure you're var-scoping your variables in CFCs where appropriate. As basic as this step seems, it does ultimately allow the garbage collection mechanisms to more quickly and accurately identify memory ready to be reclaimed.
I've had cases where finding a variable that should have been var-scoped but somehow fell through the cracks -- a variable that held a large tree of objects -- drastically changed the memory footprint of the whole app. best k On 4/18/06, Jon Gunnip <[EMAIL PROTECTED]> wrote: > This also happened to us once in over a year of generating PDF's using > cfdocument. We traced it down to a PDF request. After that request, > CPU shot up over 50% (it's usually around 10%) and stayed at that > level. No PDF's could be generated until we restarted the CF > services. > > Jon -- -- Kenneth S. Redler [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:240193 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
