@Dhivya, I'm afraid this is just a possible limitation in using the Memory Tracking. It's a very resource-intensive operation. It works fine in development, and I've even seen some production sites use it also, but most experience what you have. The general consensus is just to avoid that feature in such a case.
But there are a couple of other thoughts to consider. One is that you absolutely DO NOT need to start memory tracking in order to view the use of memory by CF (in aggregate). Go to the Memory Usage Summary page (in the Monitor, under the "Memory Usage" section on the "Statistics" tab) to see a graph of memory usage over recent time.
Similarly, you can even see what simple variables are set in the session, application, and server scopes by viewing the corresponding pages for those in that "Memory Usage" section. You just won't see complex objects (queries, CFCs, arrays, etc.) in there without memory tracking turned on. Sadly, that has misled some who misunderstood that they weren't really seeing "all" variables in a given session, application, or the server scope. You also won't see any of the things that purport to show "size" with regard to memory. They'll be 0.
But the bottom line is that the server monitor is still extremely useful without having that start memory tracking enabled. I wrote a 4-part series of articles for the Adobe Dev Center on the server monitor, which may help some readers. See http://www.carehart.org/articles/#2007_2 for the link to the first article, which points then to the others. Or you can skip to the other articles via links there on my site.
One last thing I'll add, which most miss: you can use the "filter settings" feature (a tab within the settings button at the top of the monitor) to limit what code directories are monitored at all by the server monitor. In that case, you may find that you can turn on memory tracking while monitoring only THOSE pages you're interested in. I've not yet worked with someone who had the problem and was willing to turn it on to try this (since if it doesn't work, it can crash the server). If you do it, and it works for you, please let us know. (If it doesn't, notice also the "profile filter" option to try instead.)
I do discuss these settings in the 4th article in the series, if you need a little more help in finding and using them (though at the time I did not discuss using it specifically to get around this occasional problem some have.)
Hope that's helpful.
/Charlie (troubleshooter, carehart. org)
1
Reply
AdChoices