"kyleabaker" wrote:
...I would like to log out memory usage if thats possible to monitor the debug console while using the channel so I can rule out a memory leak... or hopefully pin-point the leak.
The only way I've found to
indirectly look at memory usage is by running garbage collection
in the debug console to see a total number of brightscript component instances
http://sdkdocs.roku.com/display/sdkdoc/Brightscript+Debug+ConsoleYou can send a cancel signal to the debugger (Ctrl+C) to halt execution,
then execute 'gc' to run the garbage collector which outputs the number of 'bscs' aka brightscript components.
This isn't the best solution, but it gives you
some idea of your memory usage and you will be able to monitor if this number gets out of hand.
For more detail on the components themselves, you can run 'bsc'.
Hope this helps, let us know if you find a better solution!