Re: At least one memory leak problem is a custom combo box I use.

it. From: Mick Powell Sent: 2/2/19 10:07 AM To: users@flex.apache.org Cc: "pa...@compuace.com" Subject: Re: At least one memory leak problem is a custom combo box I use. Hello Paul, I noticed a similar problem years ago in the flex 4.1 SDK, but it could have been there for a wh

Re: At least one memory leak problem is a custom combo box I use.

entApplication function, which is then stored in a "private var". This parentApplication private var never gets cleared so it is a reference to a public function in the module causing the module to not be GCed. Not the smartest code I ever wrote, (hindsight is 20/20) but it does make things r

Re: At least one memory leak problem is a custom combo box I use.

s run faster, until the memory leak wreaks havoc. I have started to rewrite this as a class which is instantiated in the module, but stores/reads its data in/from the parent application. I have tested it with a small live module (one query/combobox) and it seems to work. I am converting anothe

Re: At least one memory leak problem is a custom combo box I use.

Paul: I assume that means that your custom combobox is still causing a memory leak? IIRC, you have a test setup where you click a button to unload the module. Add another button that checks the number of children of systemManager.popupChildren.numChildren. That number should go up by one

Re: At least one memory leak problem is a custom combo box I use.

)623-4588 From: Alex Harui Sent: 2/2/19 1:55 AM To: "users@flex.apache.org" , "pa...@compuace.com" Subject: Re: At least one memory leak problem is a custom combo box I use. Hard to say for sure, but one thing to watch out for with Comb

Re: At least one memory leak problem is a custom combo box I use.

Hello Paul, I noticed a similar problem years ago in the flex 4.1 SDK, but it could have been there for a while before that. We used a pretty simple workaround that you could try: https://mickpowellstips.blogspot.com/2010/11/dropdownlist-memory-leak-flex-41.html. It might fix your issue

Re: At least one memory leak problem is a custom combo box I use.

Hard to say for sure, but one thing to watch out for with ComboBox is running any code that accesses the dropdown property.ComboBox by itself should know how to destroy and unhook the dropdown, but if you run code that access dropDown after ComboBox thinks it cleaned up, then it will get

At least one memory leak problem is a custom combo box I use.

Alex: I have found that using a custom combo box I built causes the module that contains it to stay in memory. If I create a new instance but do not access it, everything is fine, As soon as I touch the dataprovider, it will not allow the parent module to unload (even if I set the

Re: Debugging memory leak in Flex 3.5

the module to unload. HTH, -Alex On 1/30/19, 1:12 PM, "Paul Stearns" wrote: Alex: I have a group of 10 Sent: 1/30/19 3:31 PM To: "users@flex.apache.org" , "pa...@compuace.com" Subject: Re: Debugging memory leak in Flex 3.5 Paul, In

Re: Debugging memory leak in Flex 3.5

Alex: I have a group of 10 Sent: 1/30/19 3:31 PM To: "users@flex.apache.org" , "pa...@compuace.com" Subject: Re: Debugging memory leak in Flex 3.5 Paul, In step 3, when they click the X and ModuleLoader unloads the module, do you see the module unload in the debugger

Re: Debugging memory leak in Flex 3.5

Paul, In step 3, when they click the X and ModuleLoader unloads the module, do you see the module unload in the debugger player? I think you would see a line like [UnloadSWF] in the debugger console. In step 4, are the "children" you refer to the child UI widgets of the module? One technique

Debugging memory leak in Flex 3.5

I started down this path some time ago, when I ran into a dead end and other projects piled up, I needed to abandon the hunt for memory leaks in my application. I am now 100% focused on solving this as it has gotten to be a real problem. I use FlexBuilder 3 as a tool. I am not opposed to using

Re: Memory Leak

Unfortunately, you can't override event listeners in Flash. But the framework code is theoretically designed to not cause pin modules in memory when used "properly". The ComboBox dropdown probably isn't the culprit here, I was mainly using it to illustrate that your clean up code can't clean

Re: Memory Leak

Alex, I took a different but similar approach. I created a small class, and kept adding stuff to it until it failed. I determined it failed using the profiler. I did this back in December, but resolving this seems like it will take a fair amount of dedicated sleuthing. Large blocks of time can be

Re: Memory Leak

AIUI, no. If ValidatedComboBox subclasses mx.controls.ComboBox but doesn't override the DropDown, then the dropDown will make itself a child of the Stage and may also attach a listener to the Stage (stage.addEventListener). I don't think your code can override the Stage's addEventListener so

Re: Memory Leak

I never use combobox directly, I always use "ValidatedCombobox" which has my clearEvents method in it. Both ValidatedComboBox as well as the class (the module that is loaded) that has the code; var cb:ComboBox = new ValidatedComboBox(); addChild(cb); trace(cb.dropDown); in it, have the

Re: Memory Leak

Hi, I might be missing something, but AFAICT, even if all of that works perfectly, you still don't know if your code has caused some Flex framework code to attach a listener to the stage, a Timer, a network class, etc. IOW, I think you can run code like: import mx.controls.ComboBox; var

Re: Memory Leak

In general, child UI widgets don't cause leaks unless they attach something to the stage. So ComboBox is always suspect because it has a dropDown that is attached to the SystemManager/Stage. A few other components listen for events from the stage. Also, I want to remind you that

Re: Memory Leak

This is a traditional business application. There are no videos or other gimcracks. However some of the modules have multiple tabs with close to 200 (maybe more) data entry objects, including enhanced versions of the combo box, text input, text area, etc. -- Sent from:

Re: Memory Leak

IIRC, if you can run the Flash Builder profiler, you can try to see what the references are to the objects coming from the modules. Another technique is to comment out parts of the module until it unloads. Are there any SWF assets in the modules? Animations and timer-based/interval-based code

Re: Memory Leak

To get a flavor for the application, think of a desktop application where there is a menu bar, from which you select items. These items would bring up "programs" (modules/panels) which are discreet items that perform very specific functions. When finished with the "program" it exits (unloads the

Memory Leak

I do not get my memory back in most cases. I have succeeded in creating very small modules that do very little, and they will give up their memory when unloaded, but anything beyond one or two fields causes the memory leak. The application that is currently causing the most grief has many (>

Re: Alert/PopUpManager background modal overlay memory leak

the > application performance due to memory leak. > > Anyone else facing similar issues ? > > I need to show a modal overlay to prevent the user from interacting with > the rest of the application. > > Plz share any suggestions/ links to create a lightweight modal over

Alert/PopUpManager background modal overlay memory leak

Hi All, When checking my application performance, I find that the Alert modal overlay which is the the PopUpManager 's modal overlay is impacting the application performance due to memory leak. Anyone else facing similar issues ? I need to show a modal overlay to prevent the user from

Re: Memory leak: is it a known issue ?

Hi We are getting memory leak issue when data is sent repeatedly without end point. Pls refer to issue Flex-35325 Regards, Aruna On Jun 19, 2017 10:45 AM, "Arun Kumar Padhi" <aruna.pa...@gmail.com> wrote: > Hi > We are getting memory leak issue when data is sent repeated

Re: Tomcat 8 memory leak (?) moving from GlassFish

in services-config.xml? - Original Message - From: "Christofer Dutz" <christofer.d...@c-ware.de> To: users@flex.apache.org Sent: Tuesday, January 10, 2017 5:28:46 AM Subject: Re: Tomcat 8 memory leak (?) moving from GlassFish Hi, I can’t really say if you need all of them

Re: Tomcat 8 memory leak (?) moving from GlassFish

ode get inserted into? I don't see that tag anywhere in my files. - Original Message - From: "Christofer Dutz" <christofer.d...@c-ware.de> To: users@flex.apache.org Sent: Monday, January 9, 2017 1:26:00 AM Subject: Re: Tomcat 8 memory leak (?) mo

Re: Tomcat 8 memory leak (?) moving from GlassFish

Dutz" <christofer.d...@c-ware.de> To: users@flex.apache.org Sent: Monday, January 9, 2017 1:26:00 AM Subject: Re: Tomcat 8 memory leak (?) moving from GlassFish Hi, I am using that combination and it’s working quite fine. However I already knew you were using BlazeDS, from your firs

Re: Tomcat 8 memory leak (?) moving from GlassFish

Anyone using Flex+BlazeDS+Tomcat? If so, stop Tomcat ($CATALINA_HOME/bin/shutdown.sh) and look at the log at $CATALINA_HOME/logs/catalina.out. Do you see a SEVERE error for memory leak when Tomcat stops? - Original Message - From: modjkl...@comcast.net To: "apache users&qu

Re: Tomcat 8 memory leak (?) moving from GlassFish

to use. - Original Message - From: modjkl...@comcast.net To: "apache users" <users@flex.apache.org> Sent: Friday, January 6, 2017 2:12:59 PM Subject: Re: Tomcat 8 memory leak (?) moving from GlassFish I should mention I'm using BlazeDS, which I'm assuming is creat

Re: Tomcat 8 memory leak (?) moving from GlassFish

I should mention I'm using BlazeDS, which I'm assuming is creating connections(?). - Original Message - From: modjkl...@comcast.net To: "apache flex users" <users@flex.apache.org> Sent: Friday, January 6, 2017 2:08:08 PM Subject: Tomcat 8 memory leak (?) movin

Tomcat 8 memory leak (?) moving from GlassFish

[flex.messaging.io.SerializationContext@66135428]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.

Re: Using Adobe Scout to locate memory leak

well enough OTOH to say that it is a problem. -Alex -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Using-Adobe-Scout-to-locate-memory-leak-tp7770p8003.html Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Using Adobe Scout to locate memory leak

-- View this message in context: http://apache-flex-users.246.n4.nabble.com/Using-Adobe-Scout-to-locate -memory-leak-tp7770p8003.html Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Using Adobe Scout to locate memory leak

a problem. -Alex -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Using-Adobe-Scout-to-locate-memory-leak-tp7770p7995.html Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Using Adobe Scout to locate memory leak

. -Alex -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Using-Adobe-Scout-to-locate -memory-leak-tp7770p7995.html Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Using Adobe Scout to locate memory leak

Builder can show you back-references may still be worth considering. HTH, -Alex -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Using-Adobe-Scout-to-locate-memory-leak-tp7770p7962.html Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Using Adobe Scout to locate memory leak

On 9/10/14 2:40 AM, DarrenEvans darren.ev...@allocatesoftware.com wrote: I suspected something to do with last thing thing that had focus too but couldn't determine if that was the case. I have made a bit of progress this morning in that I can get rid of it now. In the dispose() method I was

Re: Using Adobe Scout to locate memory leak

. And there are countless other scenarios where Singletons get registered and reference a child. -Alex -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Using-Adobe-Scout-to-locate-memory-leak-tp7770p7969.html Sent from the Apache Flex Users mailing list archive

Re: Using Adobe Scout to locate memory leak

. And there are countless other scenarios where Singletons get registered and reference a child. -Alex -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Using-Adobe-Scout-to-locate -memory-leak-tp7770p7969.html Sent from the Apache Flex Users mailing list archive

Re: Using Adobe Scout to locate memory leak

away. -Alex -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Using-Adobe-Scout-to-locate-memory-leak-tp7770p7971.html Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Using Adobe Scout to locate memory leak

and the top-level doesn't go away. -Alex -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Using-Adobe-Scout-to-locate-memory-leak-tp7770p7973.html Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Using Adobe Scout to locate memory leak

tests where you don't open the DateField and the top-level does go away, then you open the DateField and the top-level doesn't go away. -Alex -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Using-Adobe-Scout-to-locate -memory-leak-tp7770p7973.html Sent from

Re: Using Adobe Scout to locate memory leak

.nabble.com/Using-Adobe-Scout-to-locate-memory-leak-tp7770p7946.html Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Using Adobe Scout to locate memory leak

: http://apache-flex-users.246.n4.nabble.com/Using-Adobe-Scout-to-locate -memory-leak-tp7770p7947.html Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Using Adobe Scout to locate memory leak

in FlashBuilder, you can't always use Loitering Objects to solve a memory leak problem. There are two kinds of memory leak scenarios described on my blog [2]. Loitering objects only helps with one of them and there have been many occasions when I've had the other scenario. Fundamentally, loitering

Re: Using Adobe Scout to locate memory leak

Hi, Will have a look at that localConnection hack to see if that can aid us in finding the hanging reference. Have you tried clicking on the Force Garbage Collection icon (the garbage bin) in memory allocations tab? I find that usually narrows the issue down quite quickly. Thanks, Justin

Re: Using Adobe Scout to locate memory leak

to see if that can aid us in finding the hanging reference. Alex Harui wrote I don't think there is a loitering objects computation in Scout. Plus, even in FlashBuilder, you can't always use Loitering Objects to solve a memory leak problem. There are two kinds of memory leak scenarios

Re: Using Adobe Scout to locate memory leak

.nabble.com/Using-Adobe-Scout-to-locate-memory-leak-tp7770p7853.html Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Using Adobe Scout to locate memory leak

I don't think there is a loitering objects computation in Scout. Plus, even in FlashBuilder, you can't always use Loitering Objects to solve a memory leak problem. There are two kinds of memory leak scenarios described on my blog [2]. Loitering objects only helps with one of them and there have

Using Adobe Scout to locate memory leak

(some very small drops are seen). With the size of this app I'm just getting lost on where to really begin. Are there any decent guides on how to use Adobe Scout for memory leak detection? -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Using-Adobe-Scout

Re: Using Adobe Scout to locate memory leak

guides on how to use Adobe Scout for memory leak detection? -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Using-Adobe-Scout-to-locate -memory-leak-tp7770.html Sent from the Apache Flex Users mailing list archive at Nabble.com.

item renderers memory leak in spark.list

Hi, I'm facing with a memory leak while while setting new dataprovider for a spark list. The list is using a virtual layout but never destroys previous (custom) item renderers (extending LabelItemRenderer) when creates the new ones, so they remain stored in memory. Any ideas? Thanks Gabri / /