Adobe: Please reopen this bug SDK-30917

Question

Currently in Flex 4.5.1 if you set the VideoDisplay source over and over, each time the memory usage of the runtime (e.g. ADL.exe) increases. After a while the memory usage drops to about 50MB or so and starts increasing again. However, this time when the memory drops, the runtime stops responding. Other people have confirmed this behaviour.
Bill has provided some links to other tickets regarding the same issue, one of which I reported ages ago. The fix suggested here is to set the VideoDisplay source to null before setting the source to something else. This should free up memory. However the "null" workaround that used to work no longer works.
Can you reopen this ticket please and let me know what's happening about fixing this bug?
https://bugs.adobe.com/jira/browse/SDK-30917

Answer 1

I am having exactly the same issue. Here is simple test case:
<?xml version="1.0" encoding="utf-8"?>
<s:WindowedApplication creationComplete="creationComplete(event)" xmlns:fx="http://ns.adobe.com/mxml/2009"
                                                     xmlns:s="library://ns.adobe.com/flex/spark"
                                                     xmlns:mx="library://ns.adobe.com/flex/mx">
          <fx:Script>
                    <![CDATA[
                              import mx.events.FlexEvent;
                              protected function creationComplete(event:FlexEvent):void
                                        var timer:Timer = new Timer(1000);
                                        timer.addEventListener(TimerEvent.TIMER, onTimer);
                                        timer.start();
                              private function onTimer(event:Event):void
                                        videoDisplay.source = null;
                                        videoDisplay.source = "file:///D:\\test.flv";
                    ]]>
          </fx:Script>
          <s:VideoDisplay id="videoDisplay"/>
</s:WindowedApplication>
  The only workaround which works for me is to call System.gc() in the onTimer function. So it seems like for some reason garbage collector can't determine automatically that app runs out of memory.
Best Regards, Aleksey