[Laszlo-user] Understanding memory analysis when using _LzDebug.whyAlive()

[Gilad Parann-Nissany]

Hi 

We're trying to optimize our memory usage, not exactly find leaks but profile our memory. We are on OL 4.0.8. 

So far we've used _LzDebug.whyAlive() to analyze an application; is there a different recommended way to analyze the memory allcoation of an OL app? or are we doing the right thing? 

Attached a screenshot of an example run. We need help to understand this output: 

    • what are smoots? 
    • why do objects contain smoots? 
    • what are the numbers that start with a pound-sterling sign? in regular paranthesis like Array(4)?  with "#" like in Array(4) #262 
    • how to interpret the names on the leftmost side such as global.spriteroot? the ones after the colon? 



is there any way we can translate these into bytes of memory? we have measured total RAM used separately, but would like to know whether the result of whyAlive is a dependable measure of the breakdown of this memory... 

Thanks! 

Gilad 

Gilad Parann-Nissany 

----- Forwarded Message ----- 
From: "Ammar Tazami" <Ammar.Tazami at corp.G.ho.st> 
To: "Gilad Parann-Nissany" <gilad.parann.nissany at g.ho.st>, "Elias Khalil" <Elias.Khalil at corp.G.ho.st> 
Sent: Monday, April 7, 2008 6:52:59 PM (GMT+0200) Auto-Detected 
Subject: memory analysis small test 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.openlaszlo.org/pipermail/laszlo-user/attachments/20080409/c4da21c3/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1.JPG
Type: image/pjpeg
Size: 90850 bytes
Desc: not available
Url : http://www.openlaszlo.org/pipermail/laszlo-user/attachments/20080409/c4da21c3/1-0001.bin