Hi Stefan and Andreas,
Thank you very much for your responses.
It appears that the factor of 7 in memory consumption under IE compared
to Firefox in my application is not caused by a memory leak, and
therefore I will find no relief with qooxdoo 0.7.4 .
Unfortunately I cannot make a similar qoo
Hi all,
as some of us are currently on vacation we, the RAP team, are quite
low on resources.
We will be able to investigate incorporating the memory leak patches
within the next two weeks, including the one not yet in qx SVN
(http://bugzilla.qooxdoo.org/show_bug.cgi?id=1382).
If they prove ap
Hi!
> Can't say.
> To be honest - you (nor I) don't even know, if RAP 'switches' table-items
> on-demand - so that even your simple app suffers from the memory leak.
> (You could find out by looking at the JS though).
> And even if RAP doesn't switch and you are right with the assumption that
>
Hi Alex!
> Are there any plans to make a qooxdoo 0.7.4 release soon?
Plans are to have a maintenance release 0.7.4 in Q4/2008, see
http://qooxdoo.org/about/roadmap . But that might not be relevant for
the problems with your RAP application. According to the comments at
https://bugs.eclipse.org/bu
>> In this experiment I think that no deallocations should be taking
place,
>> as I am just creating a bunch of widgets.
>> The results show that the memory consumption of my application in IE is
>> a factor of 7 compared to Firefox. Based on your experience would you
>> blame IE guilty for t
Hi Stefan,
My application consumes a lot of memory because it allocates a very
large number of widgets. The critical structure is some sort of table
where each element is a very complex widget with several labels and
subpanels. My table has 100 of such widgets. Each one of them may be
further
IE uses more memory than all other browsers.
For a typical application I'd expect around 50-150MB on IE (but not
rising).
Just open some of the qooxdoo-demo-apps and compare them in different
browsers.
You won't fall below that with RAP - but you won't fall below that with
any other sophistic
Hi Stefan,
Thanks for your responses so far.
I'm not only concerned with the memory leaks of qooxdoo 0.7.3, but also
with the much larger memory footprint under IE compared to Firefox. My
application takes up a lot of memory under IE even without repeatedly
allocating/deallocating objects. Do
>> Do you know if qooxdoo developers are currently working to quickly
>> finish the 0.7.4 release?
How should I know ? I'm sure someone from the qooxdoo guys will answer
soon.
We are eagerly waiting for it as well.
>> improvements make their way to a RAP build by the end of this year
>> (coul
Hi Stefan,
Do you know if qooxdoo developers are currently working to quickly
finish the 0.7.4 release? Unfortunately due to memory consumption
problems we had to abandom RAP for our current project, but I had some
hopes that we could still use it for our next project if these
improvements mak
Alex,
The following todo still needs to be done on the qooxdoo 0.7.x branch,
before it doesn't leak anymore (though also in the current
0.7.x-branch-head huge improvements on memory-consumptions were done
already):
http://bugzilla.qooxdoo.org/show_bug.cgi?id=1382
On the RAP side you can hav
11 matches
Mail list logo
