AFAIK, they do not cause leaks. If you show some data or a simple test case
that indicates that they are, I will try to take a look.
On 8/30/10 8:36 AM, "lew.miller" wrote:
I've been wrestling with memory leaks and the FB4 profiler and lately have been
trying to understand activation-ob
Cache them if you want, but that might mean a higher total memory usage. It is
always a trade-off.
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf
Of tchredeemed
Sent: Friday, January 16, 2009 12:04 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Memory le
I'll second that. I've found the profiler hard to rely upon. Running
my app in a browser alongside WSMonitor seems more convincing to me,
but that might be because it gives me the answer I expect & want (ie,
no leaks).
Guy
On 26/11/2008, at 3:08 PM, Alex Harui wrote:
SDK-18076 hasn’t g
SDK-18076 hasn't got enough votes to go to engineering for investigation. Most
of the time, we find a bug in the user app. Every once in a while we find
something we missed, but it isn't SWFLoader, it is some control somewhere that
doesn't clean up. AFAIK, several folks are happily deployed u
groups.com [mailto:[EMAIL PROTECTED] On Behalf Of Guy
Morton
Sent: Wednesday, November 19, 2008 12:44 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Memory Leaks... Cumulative Memory and Memory.
I'm interested in knowing more about this too...I have an app that seems to
caus
That is the normal behaviour of the GC. It only runs, if it is
necessary. You could try loading/unloading your module 1000 times to
see if you really have a leak.
r.
On Wed, Nov 19, 2008 at 9:29 PM, sailorsea21 <[EMAIL PROTECTED]> wrote:
> Hi everyone, I think I'm having some issues with memory le
I'm interested in knowing more about this too...I have an app that
seems to cause the browser's memory to increase steadily over the
course of several hours. However, if I run WSMonitor alongside it, it
says the memory usage of my app *doesn't* increase overall (though it
fluctuates between
The Flex3 Profiler can help you find memory leaks
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of cavi21
Sent: Monday, June 02, 2008 2:10 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Memory leaks in a asyncronic operation
Alex, I appreciate your reply but I still think there's something wrong
regarding memory. I'm sending you an application that reproduces the
situation I started my earlier post with. Flex does not releases all the
memory it takes, even inducing garbage collection as I show in the demo
application.
*Tracy Spratt
*Sent:* Saturday, August 25, 2007 11:47 AM
*To:* flexcoders@yahoogroups.com
*Subject:* RE: [flexcoders] Memory leaks - binding to e4x XML?
I came across this article, wherein the author alleges that binding
to e4x XML objects cause memory leaks:
http://blog.fastlanesw.com/?p=14 <http://b
lf Of Scott -
FastLane
Sent: Saturday, August 25, 2007 1:33 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Memory leaks - binding to e4x XML?
Alex -
That is my posting, and I would hate for it to be "misinformation" in any way.
If your research turns up no evidence that
1 PM
*To:* flexcoders@yahoogroups.com
*Subject:* RE: [flexcoders] Memory leaks
There are two major memory usage scenarios in Flex. One involves
creating a new instance of a component, displaying, and later
destroying it. The other involves bringing in one or more classes of
components in a module and
oders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Tracy
Spratt
Sent: Saturday, August 25, 2007 11:47 AM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] Memory leaks - binding to e4x XML?
I came across this article, wherein the author alleges that binding to e4x XML
objects
this.
Tracy
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Alex
Harui
Sent: Saturday, August 25, 2007 2:21 PM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] Memory leaks
There are two major memory usage scenarios in Flex
There are two major memory usage scenarios in Flex. One involves creating a
new instance of a component, displaying, and later destroying it. The other
involves bringing in one or more classes of components in a module and trying
to get rid of that module later when its classes are no longer n
15 matches
Mail list logo