Hi guys,

only lets to explain the leaks. You must do something, if you click on
demo I posted you must play with it to be able to reproduce it, so
hover the pies and look to animations, after some time you notice that
it freezes for small amount of time. This freeze is running garbage
collector. Note that this freeze time is bigger and bigger when you
still hovering the pies and this means that there is a lot of memory
which is not garbage collected.

I think that this is caused by raphael object model. Just look at
sources it explains everything.

-- 
Best regards
- Petr Kobalicek <http://kobalicek.com>


2009/10/13 skar <[email protected]>:
> Hi Petr,
>> Hi Guys,
>>
>> I investigated that raphaeljs object model is not prototype based and
>> it leaks very much. Just run this demo
>> http://g.raphaeljs.com/piechart2.html and look how it leaks (just
>> hover pie chart). I know that this can be demo specific, but the
>> object-model they used is really not good for performance (creating
>> all functions when raphael instance is created).
>>
>> I measured leaking in google-chrome, after playing (2 minutes) this
>> simple demo took about 400MB. The leaked memory wasn't garbage
>> collected. Firefox behavior is similar. In my dev machine it now
>> consumes 1GB (only running this demo). I anaylzer performance under
>> Linux and Windows, the behavior is the same.
>>
>> Note that you can analyze mem usage using chrome "take snapshot", very good 
>> way.
>>
>> I think that this could be problem for qooxdoo apps.
>>
> well, I tried with firefox 3.0 on Ubuntu.
>                                      virtual   resident
> Empty firefox window:    102452 33688
> With only raphaeljs:        159824 83020
> No tab again:                  116768 47972
>
> So, it takes an added 50 MB of RAM both in the browser's virtual memory
> size and resident memory size. And if I close the tab, it still takes
> extra 15 MB, but I guess that firefox is caching stuff.
>
> Not the 1 GB or 400 MB it took for you. Don't know why/how the
> difference came about. Maybe others can check with their favorite
> browser and let us know.
>
> cheers,
> skar.
>
> --
> --
> The life so short, the craft so long to learn.
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to