Adobe Aire memory leak?

Hello everyone,
I am a windows xp home user with the lates flash player installed.
I been noticing some were memory usage when i use the adobe air flash player. Im not sure if anyone els notice this problem,
but when ever i launch a software called streamdesk. my memory suddenly jumps to 1.10 gb of memory. but,when i restart my computer my memory is back to normal. is anyone els seeing this problem? if so,we to report it to adobe air so they can fix it...

Adobe, can you hear me?
Not guaranteed when posting here. Try below instead.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Having said that, this is not a problem I see on any of the four Windows machines I work on. And it's not a problem commonly reported here. So my inclination is to suggest that something may be funky with your install.

Similar Messages

Adobe AIR memory leak loading SWFs

I was plagued by a memory leak that would crash my application after a few hours. The application had worked fine in the past but now was having issues and I thought it might have to do with using newer SDK's.
In the end I discovered that if I loaded external swf that had been compiled in debug mode, they would not clear completely on unload and cause a memory leak.
Compiling in release mode fixed the issue. Spent 3 days trying to figure it out.

Any chance you can check that out with the latest AIR?
Either way, it sounds like a bug, please report it at http://bugbase.adobe.com/ and then report the bug number here.
If you're able to provide a reproducable case that would really increase the chance that we can do something about it.
Thanks,
roymeo

Adobe Story memory leak

I am running Adobe Story online in Windows 7 Ultimate, 64-bit, using the application on my desktop. In the Task Manager, the Memory for Adobe Story constantly increases. At the moment it's 160,000 KB and climbing. If I leave it open for any length of time, all functions in it slow way down, apparently the result of what appears to be a memory leak.
Jeff Sengstack

Adobe, can you hear me?
Not guaranteed when posting here. Try below instead.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Having said that, this is not a problem I see on any of the four Windows machines I work on. And it's not a problem commonly reported here. So my inclination is to suggest that something may be funky with your install.

Air memory leak?

I have an application that runs all the time and listens to a blazeds channel as a consumer. When it gets a message, it draws some graphs, then captures those as byte arrays and sends them to the server to be saved as png files. However it keeps crashing after running for several hours, sometimes more than a day.
The app erases all of the charts which are drawn each time a new message is received. This is done, via removeAllChildren(). From what I've read, adding and removing children may cause memory problems in AIR. Is this true? And if so, how can I get around it? If not, what could be causing the problem? Here is a screenshot of the console error for when the app crashes (I'm using Mac OS 10.5, Sentinel is the name of the application in the log):

Well, System.gc doesn't work. Does anyone have any ideas about how to fix this?

Image Memory Leaks in AIR app

We are implementing an AIR application that loads thumbnails
from the hard drive and uploads them to a remote server.
When bringing in large images, for example, when importing
five 2MB files into Image objects:
Flex reports that it is using 55MB
Windows reports using 220 Meg (viewing memory usage of
adl.exe in task manager)
After deletion of these image objects, the memory stays
allocated!! It is released when the application is closed.
Two issues I see:
1. Huge memory usage for image objects (I understand that JPG
files are exploded into BMPs). It limits our ability to load 10's
or 100's of images.
2. Bad Memory leak
OTHER THINGS WE TRIED:
1. Displaying images as inline html IMG tags.. Same memory
usage!
2. Taking a snapshot of the image and displaying that.
Problem, used way to much CPU
I hope these issues will be fixed before release time or we
are hosed.
PLATFORM: Windows XP Professional, service pack 2

Hi
Have you tried the FB3 profiler to investigate why memory is
not getting deallocated?
You can use the loitering objects panel to track the back
references for the objects in memory. If you find that image object
is not being referenced by anything else. Can you file a bug at
http://bugs.adobe.com/flex
with a small test case.
Also as you know that jpg will be translated into bitmap. The
amount of memory required will be determined by the pixels in the
image. Each pixel will be 4K
Thanks,
Gaurav Jain
Flex SDK Team

Fixing Memory Leaks in AIR App?

Hi Friends,
I'm been facing this memory leaks issue in our app and this has taken enough of our time and resources and we are not being able to find a solution for it.
I have identified the problem in the module where we primarily need memory related fixes which is - We are setting Repeater's recycleChildren() property to true/false based upon certain conditions which we cant change. Now when this property is set to false Repeater is supposed to be removing its last created objects from memory and creating fresh ones. In our case repeater is unable to delete those. When I managed to get their instances (using createdChildren()) and freed them in code I called System.gc() for releasing the memory back to OS. Now what is happening is that this approach works fine when I run the app from code but when I create its installer (from Installsheild) and formally out in on machines it does not work. I came to know the reason from following blogs:
http://jvalentino.blogspot.com/2009/05/flex-memory-issue-3-garbage-collection.html
http://gskinner.com/blog/archives/2006/06/as3_resource_ma.html
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/system/System.htm l#gc()
http://stackoverflow.com/questions/192373/force-garbage-collection-in-as3
http://gskinner.com/blog/archives/2006/08/as3_resource_ma_2.html
Guys, can anyone of you suggest what should I do here? This has become a delivery bottleneck and we need to give a fix where the memroy is released periodically and efficiently so that the end user's system does not hang.
Please help.
Shubhra

Are you sure it doesn't ? Maybe flash does release memory but the OS leaves it assigned as described in the below comment from http://www.mikechambers.com/blog/2008/08/06/what-are-your-biggest-issues-with-adobe-air/co mment-page-3/#comment-26330
"I just finished doing more experiments, I looks like the AIR app does free the memory, but the OS leaves it assignned to the app process, until other apps requiere that memory. So, looks like it is a natural behaviour and the memory leak is not as terrible as I thougth."

Memory leaks while playing mp3 in air 1.5

Hello,
I am trying to develop an mp3 player using Adobe Air (html + javascript). When I repeatedly load files using Sound class, memory usage is constantly increasing. I have observed this on OS X 10.6. using Activity Monitor. Air runtime is 1.5.3.9120
Steps to reproduce:
1. Load the sample below with adl
2. Click on play. Observer memory usage of adl in Activity monitor
3. Click on stop. The memory doesn't get reclaimed.
Keep repeating steps 2 and 3 and observe the memory in Activity monitor.
Any ideas as to why this happens? What am I doing wrong?
Regards,
Sasa
The example:
<html>
<head>
    <script type="text/javascript" src="AIRIntrospector.js"></script>
    <script type="text/javascript" src="AIRAliases.js"></script>
    <script type="text/javascript">
      function play(){
        var req = new air.URLRequest("file://test.mp3");
        snd = new air.Sound(req);
        //channel = snd.play();
      function stop(){
        //channel.stop();
        //channel = null;
        snd = null;
      function init(){
        document.getElementById('play').onclick = play;
        document.getElementById('stop').onclick = stop;
    </script>
</head>
<body onload="init();">
    <div id="play">play</div>
    <div id="stop">stop</div>
</body>
</html>

Normally I would agree about letting the gc collect. However, in my case, memory usage increases to 300 MB after 8 hours of playing. It seems that GC didn't collect or I have some more leaks.I didn't have the time to investigate this some more.
However, if gc doesn't collect for such a long time (possibly because there is more than enough free memory), I would prefer to invoke collection myself. If for no other reason, than because it doesn't look good for the end user to have perception that my app is using 300 MB when other applications are using only couple of MB up to 100 MB in the worst cases.

Memory Leak Issue for Adobe Access iOS API

Hi,
We are trying to develop an iOS app (with ARC enabled) using Adobe Acces API 4.0 and we have identified that the function [drmManager createDRMSession] has memory leak.
DRMSESSION = [drmManager createDRMSession:METADATA playlist:PLAYLIST error:nil complete:^() {}];
We are using:
DRMSESSION -> weak
METADATA ->strong (as need to share within object)
PLAYLIST ->strong (as need to share within object)
After calling this function, the object is unable to dealloc and most of the leaking object related to networking (such as CFNetwork...)
Is this a known issue for the Adobe Access iOS API or we are missing some key steps.
Any suggestions is appreciated. Thanks in advance.

ans0600, sorry about that, I read Hiroshi's forward too quickly. I've done a little digging and have come up with two work-arounds:
Create a file with ARC disabled to translate the returned object to be an autorelease
declare the returned DRMSession as __unsafe_unretained and use CFRelease, as noted on stackexchange
In the future we may change this method to return an autoreleased object to avoid this issue. Let us know if you have any further questions!

Memory Leak in Adobe Premiere CC on Windows

I installed Premiere CC on Windows 7 ( Intel Core i7-3770K [email protected] GHz, 16GB RAM). Software has a serious memory leak. After less than hour working on a very simple project (no rendering, no effects) memory usage reached 15 GB, at which point Premiere stopped responding. After closing and reopening software memory usage again started to increase. I was testing it by just scrubbing over timeline, no editing, memory usage still slowly crept-up. I called Adobe technical support, they tried to tell me, that this is normal. Right! It is normal to be forced to close and reopen application every hour? I do not think so. I have Premiere CC also installed on my MAC Book Pro, checked memory usage on much bigger project, it was steady, not creeping up, using beween 1 and 2 GB. I checked forums for this problem, there are several posts, but have not found any response from Adobe regarding this.
Update:
Tonight I continued working on same small project, within 2 hours I had to shut down Premiere 3 times. I also limited in setting memory Premier can use, that did not make any difference, usage by Premiere went to maximum - total 16 GB with about 2 GB taken by system and other stuff running. I am monitoring memory usage on resource monitor. Used Physical memory went 100 %, Commit Charge about 60%. This so far happened three times in a row.
Adobe, can you hear me?
Milan
Message was edited by: milan-to
Message was edited by: milan-to

Adobe, can you hear me?
Not guaranteed when posting here. Try below instead.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Having said that, this is not a problem I see on any of the four Windows machines I work on. And it's not a problem commonly reported here. So my inclination is to suggest that something may be funky with your install.

Memory Leak Problem at Adobe LiveCycle Server 9.0

Hi All,
We want to upgrade our system to 9.0. During the performance test we have found memory Leak problem at ALS 9.0. I explain the detailed problematic issue below. Is there any body who has any suggest?
We have Adobe Livecycle ES2 9.0 SP2 installed on WAS 6.1. But also WAS on Windows Server 2008 R2. We call java web services from .Net Web service for generating PDFs.
On Java side “com/adobe/internal/pdftoolkit/services/javascript/GibsonMemoryTracking” class is causing Memory Leak problem at server.
Our .Net Codes. I copied below. First we generate PDF then we convert this pdf to static pdf.
First We call the GeneratePDF function.
public static bool GeneratePdf(Document document, byte[] pdfTemplate)
        try
            //Create a FormDataIntegrationService object and set authentication values
            FormDataIntegrationService formDataIntegrationClient = new FormDataIntegrationService();
            formDataIntegrationClient.Credentials = new System.Net.NetworkCredential(Settings.ALCUserName, Settings.ALCPassword);
            //Import XDP XML data into an XFA PDF document
            ALCFormDataIntegrationService.BLOB inXMLData = new ALCFormDataIntegrationService.BLOB();
            //Populate the BLOB object
            inXMLData.binaryData = System.Text.Encoding.UTF8.GetBytes(document.XmlData);
            //Create a BLOB that represents the input PDF form
            ALCFormDataIntegrationService.BLOB inPDFForm = new ALCFormDataIntegrationService.BLOB();
            inPDFForm.binaryData = pdfTemplate;
            //Import data into the PDF form
            ALCFormDataIntegrationService.BLOB results = formDataIntegrationClient.importData(inPDFForm, inXMLData);
            document.PdfData = results.binaryData;
            Utility.Log("GeneratePdf", "Pdf generated successfully.", LogLevel.Info);
            return true;
        catch (Exception ex)
            document.ReturnCode = "22";
            document.ReturnMsg = "Exception on generating the pdf";
            Utility.Log("GeneratePdf", "Exception: " + ex.Message, LogLevel.Error);
            return false;
Then We call the ConvertPDF function.
public static bool ConvertPdf(Document document)
        try
            //Create a OutputServiceService object
            OutputServiceService outputClient = new OutputServiceService();
            outputClient.Credentials = new System.Net.NetworkCredential(Settings.ALCUserName, Settings.ALCPassword);
            //Create a BLOB object
            ALCOutputService.BLOB inData = new ALCOutputService.BLOB();
            //Populate the BLOB object
            inData.binaryData = document.PdfData;
            //Set rendering run-time options
            RenderOptionsSpec renderOptions = new RenderOptionsSpec();
            renderOptions.cacheEnabled = true;
            //Create a non-interactive PDF document
            ALCOutputService.BLOB results = outputClient.transformPDF(inData, TransformationFormat.PDF, PDFARevisionNumber.Revision_1, false, null, PDFAConformance.B, false);
            document.PdfData = results.binaryData;
            Utility.Log("ConvertPdf", "Pdf converted successfully.", LogLevel.Info);
            return true;
        catch (Exception ex)
            document.ReturnCode = "22";
            document.ReturnMsg = "Exception on converting dynamic pdf to static pdf";
            Utility.Log("ConvertPdf", "Exception: " + ex.Message, LogLevel.Error);
            return false;
Our System Configuration:
Expiry date: Never Version: 9.0.0.0,
GM Patch Version: SP2
Service Pack Version: unknown
ADOBE® LIVECYCLE® PDF Generator ES2
9.0.0.0
SP2
ADOBE® LIVECYCLE® Reader Extensions ES2
9.0.0.0
SP2
ADOBE® LIVECYCLE® Output ES2
9.0.0.0
SP2
We changed some configuration which is suggested by Adobe. But this change does not solve our problem.
Changed Configurations via ADMINUI
Memory Leak Problem which is viewed via wily tool:

Hi Mahir,
Can you attach the results of this performance test where we can see how GibsonMemoryTracking class is causing the memory leak issue.
Also do you see any stackTrace in the LiveCycle server logs related to memory / heap when you run this performance test ?
Thanks,
Simer

Adobe Reader 8 memory leak

There seems to be a private byte memory leak with Adobe Reader 8.0.0 and 8.1.2 (tested both) when you try to print a PDF document. If you monitor the private bytes usage of the AcroRD32.exe with perfmon and then try to print you will see the memory usage jump and it does not come back down after the print job. In fact, it keeps on rising as you keep on sending a new print job. The only way to release the memory is to close the document and reopen it.

>I have more than 700 MB virtual memory.
That's probably not enough for normal operations. A couple of
gigabytes is safer.
There may be a problem, though. This doesn't sound like normal
behaviour. Acrobat may be cacheing text - does the size stop
increasing if you search for something, and find it, on the LAST page?
Aandi Inston

AIR runtime Memory Leak?

Hi,
I have an app developed with AIR 3.7 for iOS (iPad)
The app gets very sluggish after a while, eventually crashes.
I've been -very- careful to pool objects where possible and cleanup / nullify all objects once they're not needed any more.
Profiling the app in Scout returns a pretty stable memory profile (the peaks and the lows translate very well to what's happening on screen)
Simultenously profiling the app using XCode's Instruments, shows me that the memory consumption off the app constantly rises up to the point the systems spends more time throwing memory warning than anything else.
Here are screenshots of both profilers: they show as3 memory usage being pretty stable, on the app level, memory keeps rising...
https://dl.dropboxusercontent.com/u/608333/AIR_memory_leak.zip
If AS3 is not leaking any memory (according to scout), but the app is (according to Instruments), would I be right assuming there's a memory leak in the AIR-runtime itself?
thanks for your feedback!
bart.

ok, lots of trial and error has showed me the following:
There are two issues when loading assets using the Loader Class with its LoaderContext set to ImageDecodingPolicy.ON_LOAD.
These issues typically arise in a magazine-like app, where many images are loaded and unloaded continously.
Issue 1:
When initializing a load() on a Loader class with LoaderContext to ImageDecodingPolicy.ON_LOAD, all image decoding seems to be queued in a seperate thread. With several large images, especially on mobile devices, the time to crunch through a queue like this can easily go into dozens of seconds. During that time, some of the loaders can be unloaded, cleared, nulled and deleted. Yet, the loader isn't removed from the decoding queue.
In other words: once you fire the 'load' method on a Loader instance, you're not able to cancel the decompression process, even though the decompression might not even have started yet, as queued by other decompressions.
Issue 2:
When a Loader instance is unloaded, cleared, nulled and deleted while its decompression is still queued and not yet fully decompressed, there seems to be a memory leak. With several dozens of images loading and interupting the loading, you'll notice a difference in memory consumtion when comparing memory output in Scout and in Instruments. Both memory graphs build up very similar yet after the runtime's garbarge collection kicks in, the memory graph in Instruments seems to not release memory fully. Consumption gradually rises until the app eventually crashes.
https://dl.dropboxusercontent.com/u/608333/AIRMemoryLeakExample.zip
This example app allows you to create loaders in bursts by touching the screen.
You'll instantly see the massive waiting times for decompression, despite the fact there's only a few Loader instances in memory at the same time. After several short bursts and wait-a-bit-for-decompression-to-catch-up, you should also notice the difference in memory profiling between Scout and Instruments.
I managed to work around both issues by making a LoaderQueueManager class.
This class instantiates and returns a Loader instance, queues these instances and tracks its onComplete handler. Only when one loader is finished loading, the next loader starts loading. This way, you never have different instances trying to simulataneously decompress their content. As such decompressions are never interrupted and loaders can also be de-queued. This practically speeds up decompression dramatically, since images that are removed won't get decompressed in vain. Memory Leaks also don't occur, since not a single decompression is ever interupted.
This solution only works with content loaded locally.
Hope you can get somewhere with this,
and hopefully, you find a fix in one of the next AIR releases.
best,
bart.

Memory leak on latest Adobe Reader 8.1.2 Win XP SP2

Dear Adobe Developers,
I have encountered a strange problem. I open a PDF file of size about 16.5 MB, I search trough it and then the memory allocated starts steadily growing until it fills out the entire RAM and the virtual memory as well. Strange thing is this only happens after I perform a search through the file; if I don't do it, all stays within normal. I was wondering if it is not a memory leak of some kind? I use Adobe Reader 8.1.2 on Win XP with Service Pack 2 on Celeron 1.7 GHZ, 256 DDR RAM, 320 GB HDD ect .. Normally the RAM occupied by the OS itself is only about 100 MB so there are ~150MB left free. But they seem not to be enough even when we add to them the virtual memory.
Greetings,
Georgi Popov, BG

>I have more than 700 MB virtual memory.
That's probably not enough for normal operations. A couple of
gigabytes is safer.
There may be a problem, though. This doesn't sound like normal
behaviour. Acrobat may be cacheing text - does the size stop
increasing if you search for something, and find it, on the LAST page?
Aandi Inston

Adobe AIR only consume 1.5Gb of memory... WHY?????

I made an app id Adobe Flex that needs a large quantity of memory to process PHOTOS i have a PC with windows 7 x64 with 16Gb of memory but Adobe AIR only use 1.5Gb WHY???
Thanks
HUGO

Oh you want your app to use mroe than 1.5 Gb of memory.. Didn't understand your question.
Well it is not Adobe fault... You shouldn't go over 1.5 gb of memory for any consideration... It crash because Windows 32 bits give each application a max of 2gb memory adress space. If you try to get more memory than that limit, Windows refuse and kill your application.You see 1.5 gb, but if you add the dll and all system memory usage for AIR, you probably reach 2gb.
More details in the correct answer of this question : http://stackoverflow.com/questions/5684846/c-application-crashes-once-it-memory-usage-reac hes-1-5-gb
This means you must do a better job at handling the memory in your application.

Memory Foot Print OF Adobe Air Application

I have to create adobe air application for peer to peer application which will be run on (gateway)embedded Linux.
The problem is memory in the device is very low <= 2 mb.
I wanted know what is the memory foot print of the adobe air application if the code size is 200kb.

Hi, here is an update to my problem.
After enabling legacy CAS policy in my configuration file, the memory is released immediately!
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<runtime>
<legacyCasPolicy enabled="true" />
</runtime>
</configuration>
I am still hoping to receive feedback about the problem. What is going on? Is this the right solution? Will it work in the future?
Is it because our project has to run only as a 32-bit process?
Thanks in advance
Michel Miranda

Adobe Aire memory leak?

Similar Messages

Maybe you are looking for