In the last version of fullcalendar at line 163 :
element.data('fullCalendar', calendar); // TODO: look into memory leak
implications
Richard
On Fri, Sep 21, 2012 at 5:30 PM, Richard Vézina <ml.richard.vez...@gmail.com
> wrote:
> Leak seems to come from FullCalendar itself since I load the page with
> blank init of fullcalendar and get the leak :
>
> <script type='text/javascript'>
> jQuery(document).ready(function() {
>
> var date = new Date();
> var d = date.getDate();
> var m = date.getMonth();
> var y = date.getFullYear();
>
> $('#calendar').fullCalendar({
>
>
> });
>
> });
> </script>
>
> I try to upgrade to last version of fullcalendar (also upgrade jQuery to
> make sure) nothing better...
>
> I realize all the testing under 1.99.4, anyone can confirm with other
> version??
>
> Thanks
>
> Richard
>
> On Fri, Sep 21, 2012 at 3:23 PM, Richard <ml.richard.vez...@gmail.com>wrote:
>
>> Hello,
>>
>> I test AppointmentManager app this morning and I found there is a memory
>> leak when reloading repeatedly mycal page. The python process that hold
>> web2py keep growing slowly (~5 meg) each time the page is reloaded.
>>
>> The app I am talking about is available here : http://web2py.com/
>> appliances
>>
>> Can be downloaded here :
>> https://github.com/mdipierro/web2py-appliances/blob/master/AppointmentManager/web2py.app.AppointmentManager.w2p
>>
>> Richard
>>
>> --
>>
>>
>>
>>
>
>
--
