flex - Spark Combox Memory Leak -

-

i have simple, reproducable memory leak associated spark combo box, i'm convinced must i'm doing wrong, rather sdk bug.

// application.mxml <?xml version="1.0" encoding="utf-8"?> <s:application xmlns:fx="http://ns.adobe.com/mxml/2009"                 xmlns:s="library://ns.adobe.com/flex/spark"                 xmlns:mx="library://ns.adobe.com/flex/mx">     <s:layout>         <s:verticallayout />     </s:layout>     <fx:script>         <![cdata[             import mx.events.flexevent;              private var haselement:boolean;             protected function togglecontainer():void             {                 if (haselement)                 {                     button.setfocus();                     comboboxcontainer.removeallelements();                     haselement = false;                 } else {                     var vew:comboboxview = new comboboxview();                     comboboxcontainer.addelement(vew);                     haselement = true;                 }             }         ]]>     </fx:script>     <s:button id="button" label="add container" click="togglecontainer()"  />     <s:group id="comboboxcontainer" /> </s:application>   // comboboxview.mxml  <?xml version="1.0" encoding="utf-8"?> <s:vgroup xmlns:fx="http://ns.adobe.com/mxml/2009"           xmlns:s="library://ns.adobe.com/flex/spark"           xmlns:mx="library://ns.adobe.com/flex/mx"          >     <s:combobox /> </s:vgroup>

when compiled against flex 4.1, appears create memory leak, comboboxview never gc'd -- because of lingering reference combobox.

here's output profiler: enter image description here

steps reproduce:

  • create project application.mxml , comboboxview.mxml
  • compile project flex 4.1
  • launch application.mxml profiler
  • create memory snapshot
  • click button add view stage
  • click button again remvoe view stage
  • run garbage collector
  • create memory snapshot
  • view lingering objects between 2 memory snapshots

note - doesn't occur when application compiled against flex hero.

it appears though bug, cannot believe combobox has memory leak -- surely would've been fixed before 4.1 shipped?

what doing wrong here? why isn't view being gc'd?

update i've done further investigation this, , believe issue lies in problem richeditabletext component comboboxskin uses. see details here: spark memory leaks

http://www.iampj.com/search/label/combobox%20memory%20leak

i have been having similar problems in flex 3


Comments

Post a Comment

Popular posts from this blog

javascript - Enclosure Memory Copies -

-
function myclass() { //lots , lots of vars , code here. this.bar = function() { //do numerous enclosed myclass vars } this.foo = function() { alert('hello'); //don't enclosed variables. } } each instance of myclass gets own copy of bar , foo, why prototyped methods use less memory. however, know more memory use of inner methods. it seems obvious me (1) below must true. agree? not distinct myclass instances have own distinct copies of bar, must have own distinct copies of myclass enclosure. (or else how bar method keep myclass variables straight on per instance basis?) now (2) question i'm after. since inner foo method doesn't use in myclass enclosure natural qustion is: javascript smart enough not keep myclass enclosure in memory use of foo? this depend entirely on implementation not language. naive implementations keep far more around others. answer true e.g. v8 (chrome's js engine) may not true spider...
Read more

php - Replacing tags in braces, even nested tags, with regex -

-
example preg_replace('/\{[a-za-z.,\(\)0-9]+\}/', 'replaced', 'lorem ipsum dolor sit {tag1({tag2()})}, consectetur adipiscing elit.'); the result: lorem ipsum dolor sit {tag1(replaced)}, consectetur adipiscing elit. question as can see "tag2" has been replaced, want replace "tag1" know how can this? (in cases might this: {tag1({tag2({tag3()})})}) , on.) btw using preg_replace_callback, easier show preg_replace here site can test code: http://www.spaweditor.com/scripts/regex/index.php you need add curly braces character set. here's pattern used: /\{[a-za-z.,\(\)\{\}0-9]+\}/ and here result: "lorem ipsum dolor sit replaced, consectetur adipiscing elit."
Read more