Or at least install the FlexBuilder Eclipse plug-in into your existing
Eclipse installation. Yes,
- Raju
On Feb 17, 2009, at 4:43 PM, Sebastian Wagner wrote:
yes I've seen that tool, but I think you have to use also Flex
Builder to use it.
sebastian
2009/2/17 Raju Bitter <[email protected]>
Hi,
Flex-Builder Professional has a profiling tool, there's more info
here.
http://labs.adobe.com/wiki/index.php/Flex_3:Feature_Introductions:_Performance_and_Memory_Profiling
But that's the expensive version, start at $ 699,-
- Raju
On Feb 17, 2009, at 3:52 PM, P T Withington wrote:
On 2009-02-17, at 08:08EST, Sebastian Wagner wrote:
hi,
I would like to profile my application cause they consume sometimes
more
memory that they should, memory consumption rises without any
obvious reason
or interaction.
What kind of memory monitoring can we do in OpenLaszlo?
I know that you can somehow mark objects in the debugger and then
later on
print this list again. But that would mean you have a very big
workload in
analyzing xxxx elements. Although I don't think that this will
actually tell
you everything.
The debugger memory tracing http://xrl.us/begjnk is not intended as
a profiling or monitoring tool, but as a way of helping you find
'leaks' in your program. Leaks typically are because you have a
global structure that is accumulating references to objects which
_should_ be recycled.
You don't really need a big work load to do this. You just need to
exercise your program in a normal way and use the tools. Usually if
your program is growing without bound, the leak tools will make it
obvious where your leak lies.
The documentation on how to use these tools is a little sparse. I
will make a task to improve it with an example.
[Unfortunately, these leak tools only work in swf8 and DHTML.]
What kind of third party Tools can be used in the different runtimes?
Or are there any *down to earth* experiences/use cases/cook book of
people
who run into the same problem.
Most people start by using their OS memory tools and noticing that
their app grows and grows. Then they will use the Debug tools to
find the leak in their app.
Sometimes, the leak is in the LFC runtime; but we have worked hard
to control that. Running in DHTML on IE is particularly difficult
because IE has a very poor garbage collector.
Will this change with AS3... or are there additional ressources to
monitor
Memory in the future OpenLaszlo Versions?
Because OpenLaslzo just creates a swf9 program, you can use the Flex
tools and the debug version of the Flash player. I have not (yet)
tried to do this, but perhaps there are other community members out
there who have.
--
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.laszlo-forum.de
[email protected]
