Air runtime memory usage

I am developing games on Android devices and I find the total memory usage of my air application presented in Scout is always smaller (100M) than the memory usage shown in the Taskmanager.
Some articles say that the Scout does not count the memory used by the air runtime.
However, it is not possible that the air runtime occupies more than 100M memory, right? Especially, on Android devices?
I have also written a very small test app, it only occupies 20M memory (containing the air runtime).
My question is how can I reduce the additional 100M memory not presented in Scout?

Similar Messages

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 usage in Thread wait()

Hi all,
I have a question.
What is the memory usage (in terms of RAM, not of virtual memory) if 1000 Threads wait for a long time on a common object suppose for more than one day?
Will be they moved to disk memory and then in RAM when a notify() occurs or what else? Thanks! Bye

Ok,
I understood your answers but I see the scenario is not clear.
Suppose a program has to launch and high number of threads. Some of these threads will wait on a monitor for a large period of time (in terms of days...) and others will have no wait at all.
Eg. Think as half the threads that run on the JVM blocks on a monitor and the other half not. Suppose we create 1000 thread every 5 second.
So we have this kind of evolution in one minute
12 * 1000 Threads are created
12 * 500 Thread will wait on a monitor (for a very long time)
What the JVM does with this thread? Will the JVM move this threads for RAM to disk or will it keep them in RAM?
In other words, what is the runtime memory usage of the JVM when a thread waits for a very long time? Will it temporary free the memory of the thread, saving it in the disk or will it keep it in RAM?
I hope I've been clear now! Bye

CPU/memory usage of AIR application under Mac 10.4.10

As my AIR application uses a lot of CPU/memory under Mac
(seems better in Windows), I decide to do some basic testing. I
create several applications with different level of complexities.
Below is a table of CPU/memory usage when the application is simply
sitting there. A brief description of the application can be found
in the end of each line.
Here are some results:
[1] Even for an empty application, CPU usage is not zero
(most non-AIR application has 0 CPU usage when doing nothing). Also
the memory usage is huge, comparable to Finder on my computer.
[2] Empty application has 7 threads running.
[3] Indetermined progress bar costs a lot of CPU; and I guess
any other animation costs a lot of CPU too. But if they are
invisible they are fine.
[4] running timer costs CPU.
PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE
VSIZE application
10093 adl 1.8% 0:01.85 7 100 292 15.0M 13.8M+ 22.8M 444M
empty
10094 adl 1.9% 0:01.55 7 100 299 15.2M 14.0M+ 23.1M 444M
label
10097 adl 1.9% 0:01.48 7 100 302 15.3M 13.4M 23.7M 445M
progress bar
10095 adl 5.7% 0:02.40 7 100 302 15.4M- 13.2M 23.5M 445M
progress bar (indetermined)
10125 adl 15.9% 0:03.66 7 100 304 15.7M- 13.4M 23.9M 445M 5
progress bar (indetermined)
10126 adl 29.7% 0:10.39 7 100 325 16.7M+ 13.4M+ 24.9M+ 445M
10 progress bar (indetermined)
10128 adl 1.9% 0:01.34 7 100 324 16.1M 13.7M 24.3M 445M 10
progress bar (indetermined), visible=false
10136 adl 1.8% 0:00.76 7 100 323 16.5M+ 13.9M+ 24.7M- 450M
Empty datagrid
10147 adl 1.9% 0:01.60 7 101 328 16.1M 13.8M+ 24.5M- 447M
TabNavigator with two empty VBox children
10138 adl 1.8% 0:01.59 7 100 372 19.4M 13.9M 27.7M 453M
datagrid with 10000 simple rows
10131 adl 3.1% 0:02.38 7 110 348 25.7M 19.3M 34.8M 458M 10
Empty native windows
10143 adl 1.9% 0:00.99 7 100 296 15.1M 13.9M+ 23.2M- 444M
Timer, delay = 100ms, calling an empty function
10145 adl 4.1% 0:02.35 7 100 298 15.0M 14.0M+ 23.2M- 444M
Timer, delay = 100ms, calling function update label position
As to my own application, it's much bigger than these simple
ones. The CPU usually stablizes to 20% and VSIZE is about 1G. There
is no timer running. When I leave the application open for a few
hours, the application will eventually freeze and I have to kill
it.
I am wondering if there are any articles or documents
explaining AIR's CPU/memory usage. And also if AIR is planning to
improve the performance in the next release.

James, thank you for the very fast answer! I did various tests on the weekend on my computer and computer of my friend.
And I can say, that Debug flag doesn't affect memory consumption. They still eat memory. My steps to reproduce are as follows:
(Windows 7 32 bit)
Photoshop CS5:
1) set HKEY_CURRENT_USER\Software\Adobe\CSXS2Preferences\PlayerDebugMode to 0
2*) check HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\CSXS2Preferences (just in case)
3) Compile HelloPhotoshop example to ZXP and install via Extension manager
4) restart computer
5) Run Photoshop CS5 - Memory consumption: 100 096 KB
6) Open HelloPhotoshop and close it 10 times
7) Memory consumption: 155 840 - 5,574 MB per one close/open
Maybe a garbage collector is expected to run and free this memory, but it never happened in my case. The memory pool was increasing to 1 GB when I was working with one of my panels - with no documents open in Photoshop
In InDesign I tried the same thing with HelloInDesign ( I had to close the panel completely and then open with Window | Extensions | HelloInDesign)
Memory consumption on start: 118 516
Memory consumption after 10 open/close cycles: 197 516
It's 7,9 MB per one close/open
It's the simpliest panel test. When I'm using AIR libraries the memory usage is increasing a lot faster.

CPU/Memory Usage increases when loading SWF files in AIR.

Hi,
We face the below mentioned problem. Would be great if someone could help us.
Due to problems with uploading the attachment here, please send a email to the following email-id ([email protected]) and I shall send the attachment in response.
CPU/Memory usage increases drastically while moving the SWC components and loading the SWF Files.
"Problem Description" - On executing the sample application, a window with multiple objects is shown. The loaded SWC components in flex consume too much Memory and CPU cycles. This is visible in TaskManager. On dragging one of the object, CPU / memory usage increases drastically.
"Steps to Reproduce" -
Draggable window is placed at the bottom in the sample application with Text indication.
Drag the indicated window.
"Actual Result" - System's CPU usage increasing drastically around 50% to 60 %.
"Expected Result" - Drastical increase in memory\CPU should not occur.
"Any Workarounds" - No"
Thanks in advance.

You can control your external swf from your main.swf in the following method:
loadswf(clips[0]);
function loadswf(tmp:String):void{
    passedString=tmp;
    ldr= new Loader();
    ldr.contentLoaderInfo.addEventListener(ProgressEvent.PROGRESS, progressListener);
    ldr.contentLoaderInfo.addEventListener(Event.COMPLETE, swfLoaded);
    ldr.load(new URLRequest(animPath+tmp));
    function progressListener (e:ProgressEvent):void{
        ploader.visible=true;
    function swfLoaded(e:Event):void {
        mcExt = e.target.content as MovieClip;
        ldr.contentLoaderInfo.removeEventListener(Event.COMPLETE, swfLoaded);
        mcExt.addEventListener(Event.ENTER_FRAME,onEnterfn);
        ploader.visible=false;
        addChild(mcExt);
function onEnterfn(e:Event):void{
    var num:int=mcExt.currentFrame;
    switch(passedString){
        case clips[0]:
            if (num==1) mcExt.play();
            if (num==9) {
               mcExt.skipmc.addEventListener(MouseEvent.CLICK,skipfn);
                function skipfn(e:MouseEvent):void{
                    mcExt.stop();
                   mcExt.removeEventListener(Event.ENTER_FRAME,onEnterfn);
                    gotoAndStop("help");
            if (num==mcExt.totalFrames){
               mcExt.removeEventListener(Event.ENTER_FRAME,onEnterfn);
                gotoAndStop("help");
            break;

Extensive (very very very extensive) memory usage of host application with CS extension

Hi!
I tried this only under Photoshop CS5 and InDesign CS5 under Windows 7.
When you open and close CS extension panel, the memory taken by Photoshop (InDesign) increases by 6-30MB!
In case of the simple HelloPhotoshop (HelloInDesign) panel from the examples, compiled in release mode, when you open it and close, - it's about 6-10MB each time you do it. And in case of a more complex panel, which uses AIR, etc. it's about 30MB per one panel close/open.
When I use some panels in 5-10 minutes Photoshop (InDesign) increases its memory pool from 600MB up to 1,2 GB. And more. And this memory is never freed, only until Photoshop (InDesign) shutdown.
I tried freeing all my arrays, killing display objects, etc. - nothing helped. Even a simple HelloPhotoshop (HelloInDesign) that does nothing eats memory.
By the way, InDesign eats memory a lot faster .

James, thank you for the very fast answer! I did various tests on the weekend on my computer and computer of my friend.
And I can say, that Debug flag doesn't affect memory consumption. They still eat memory. My steps to reproduce are as follows:
(Windows 7 32 bit)
Photoshop CS5:
1) set HKEY_CURRENT_USER\Software\Adobe\CSXS2Preferences\PlayerDebugMode to 0
2*) check HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\CSXS2Preferences (just in case)
3) Compile HelloPhotoshop example to ZXP and install via Extension manager
4) restart computer
5) Run Photoshop CS5 - Memory consumption: 100 096 KB
6) Open HelloPhotoshop and close it 10 times
7) Memory consumption: 155 840 - 5,574 MB per one close/open
Maybe a garbage collector is expected to run and free this memory, but it never happened in my case. The memory pool was increasing to 1 GB when I was working with one of my panels - with no documents open in Photoshop
In InDesign I tried the same thing with HelloInDesign ( I had to close the panel completely and then open with Window | Extensions | HelloInDesign)
Memory consumption on start: 118 516
Memory consumption after 10 open/close cycles: 197 516
It's 7,9 MB per one close/open
It's the simpliest panel test. When I'm using AIR libraries the memory usage is increasing a lot faster.

Very High Memory Usage

It never happened before and today it overloaded my PC so i had to force restart.
I use 2 keyword research applications. They start to shoot up to almost 600MB of RAM when i am researching keywords. When i minimize program after research, the memory usage drops to 32MB. When i restore window back, these 32MBs turn back into 600MB.
I tried downgrading Adobe Air to version 2.0.4 and that didn't help. Upgrading to the newest version didn't help.
What is the problem?

Hi Boris,
The memory usage is very dependent on the application and how it handles it's resources. Have you contacted the developers of the two applications to see if your findings are consistent with their testing? You mentioned that the memory footprint is the same between 2.0.2 and 2.5, do you know if it increased after 1.5.3?
Having the memory usage drop to a fraction of it's normal size when minimized is consistent with normal Windows behavior.
Thanks,
Chris

Excessively high memory usage by Tomcat in NT

We are facing the problem of excessive memory usage by our servlets (that call JNI functions). The memory usage seems to touch 50+ MB in 2000 Server but it drops down to 30 MB soon. But, this does not happen in NT. The memory keeps on increasing and there is a point in time when Tomcat occupies all the available memory.
We are taking care of garbage collecting the objects frequently(by calling Runtime.gc()). Is there any other way by which we can have some kind of control over the usage of memory?
Do we have to install a patch for NT (if something like this is available)?
NT Server:
PIII 500 MHz, 256MB RAM, 40GB HDD
2000 Server:
PIII 700 MHz, 128MB RAM, 20GB HDD
Tomcat:
Version 3.2.1
JDK:
Sun's JDK 1.3
Any suggestions, pointers are appreciated.
Thanks
Manish
[email protected]

Hi, Manish:
I've solved memory leak problem in JNI once. Memory leak may be resulted from inapproriate memory access in C or C++ library.
My previous problem is: I get a C byte array from Java byte array by GetByteArrayElements, however, I never call ReleaseByteArrayElements before C function return. That will let that Java byte array unable to be garbage collected. After inserting ReleaseByteArrayElements before return, it won't run out of memory again. Similar problems may happen when useless Java object's reference count not zero because NewGlobalReference without calling DeleteGlobalReference.
However, I've faced another problem in JNI (see http://forum.java.sun.com/thread.jsp?forum=52&thread=212275). I wonder if JVM release or reset memory allocated in C library. Hope it is not true.
Regards,
David Wu

Ultra high memory usage when deleting a slide show

Hallo,
I have a DVD project with several menus and slideshows and a huge flowchart. I wanted to delete one of the slide shows. What happened then was that the memory usage rised up to over 2 GB. Not the usage of the exe shown in the windows task manager under "processes", but the swap file usage.
The first time I waited for like 5 minutes, and then Encore closed itself. Without any error message.
The next time I waited as long again, but then the swap file usage went down slowly again. After that Encore refreshed its window. The flow chart was what you could best describe as "broken". Encore then stated some abnormal condition and offered me to save the file, and recommended to save it under a different file name. I clicked on "ok", but instead of a file save dialog a C++ runtime error box appeared. I click "ok" for that, then the "you should save but under a different name" box appeared again. I clicked on "ok" again, the C++ error reappeared, and after clicking on "ok" there Encore closed itself.
I made a screenshot on which you can see the high swap file memory usage and the broken flowchart. You can download the screenshot under
http://www.digitale-bibliothek.de/Downloads/ScreenEncoreDVD.jpg
I will now try to first delete all references to the slideshow in the flow chart. But as I cannot delete an asset that is still used in a slideshow or a timeline, Encore DVD should also prevent me from deleting objects that are used in the flowchart, if it is such a problem for Encore to delete the object then.
Regards,
Christian Kirchhoff

I'm a little confused as to where you tried to delete the slideshow from.
Was it from the actual Project Browser, where all the assets are listed?
Can you try deleting the surplus slideshow from there, and let us know what happens please?

Window Memory usage even after closing windows

I've included links to a test app that does nothing but
launch a window, play a sound, close window / repeat.
When application launches it uses about 20mb of memory. When
you click on the only button, it will launch a secondary window
that will simply play a wav file. (I set the volume low but you may
want to mute it :D)
After launching and closing the window several times the
memory usage goes up considerably and *never* falls back a
significant %. (I got it to about 100MB before I decided to quit
trying to increase the memory usage. Right now it's been running
w/o any user interaction since opening about 10 windows and it's
fairly stable at around 61MB (although that appears to be
increasing w/o user interaction).
Does anyone know of any methods I can use to ensure that the
memory consumed by secondary windows does not just persist forever
even after closing the window? Is there something I'm doing wrong
here?
Example Code:
http://www.vf-server.com/air/memorytest.air
(AIR)
http://www.vf-server.com/air/memorytest.zip
(source ZIP)
Note: When I *minimize* the window it looks like garbage
collection is forced and app drops back to 11MB (on restore back to
19mb).
Edit: note in your task manager, application appears as
JBTest.exe

You can call System.gc() to force the garbage collector to
run.
Try removing the event listeners when they aren't needed
anymore. I think it is more difficult for the gc to cleanup objects
when there are host objects (like Sound) refering to JavaScript
objects and JavaScript objects refering to host objects, so you
need to be especially careful about those. It SHOULD clean them up
eventually, but it may take longer for it to figure out that those
objects are no longer in use.
You might also clear the secondaryWindow reference in the
parent document when the window closes. That reference might retard
garbage collection, too.

Best practice for CPU and memory usage?

I find my AIR application takes a lot of memory -- usually
>170M. And what is strange is that the memory usage is
increasing (about 4K/s) even when the application is simply sitting
there and do nothing. The CPU usage is supposed to be 0% when the
application is doing nothing, but it's not (usually ~5%). So I
wonder if there is any article about best practice on CPU/Memory
usage.

Those numbers indicate that your application is in fact doing
something. Perhaps you have a timer still running, or work being
done on an enterFrame event?

Adobe Premiere Elements 8 Can't finish installing Air Runtime Process, and Can't open New Project!

Hey guys,
I'm having some major issues installing PE8. I can open the installer screen fine, and it installs fine until it gets to installing the Air Runtime Process. I have left it downloading that one process for about 5 hours, and i'm not exaggerating. Finnally, I get too mad waiting for it to finish that I exit out of the installation process. Even though the installation was never fully finished, for some reason I do have a Desktop icon for PE8. I click on that and it opens the splash screen with the buttons "New project", "Open Project", and "Organize". When I try to open "New Project" it begins loading the files that it needs to to open it. When it gets to loading the Windows Media file, it freezes and then crashes.
I have uninstalled the PE8 and reinstalled it about 5 times now. I have also used the Windows Cleanup program to clean these corrupted files out of my system before reinstalling. I have called in twice now to the technical support and they haven't helped me one ounce. Any answers would be appreciated! Thanks
Thanks Again,
Spencer
Here is the Crash Data:
<?xml version="1.0"?>
<!DOCTYPE crashreport SYSTEM "AdobeCrashReporter.dtd">
<crashreport version="1.1" crVersion="3.0.20090804" applicationName="Adobe Premiere Elements" applicationVersion="8. 0. 0. 0" build="unknown">
<time year="2009" month="11" day="20" hour="22" minute="57" second="2"/>
<user guid="f32bcbfe-242d-4051-8b96-487956b2e7bc"/>
<system platform="windows" osversion="5.1.2600 SP 2.0" applicationlanguage="Language Neutral" userlanguage="en_US" oslanguage="en_US" ram="893" machine="AMD Athlon(tm) 64 X2 Dual-Core Processor TK-55" model="x86 Family 15 Model 104 Stepping 1" cpuCount="2" cpuFreq="1800 MHz" busFreq="" locale="English (United States)"/>
<crash exception="EXCEPTION_ACCESS_VIOLATION" instruction="0x01a29f27">
<backtrace crashedThread="0">
<thread index="0">
<stackStatement index="0" address="0x01a29f27" symbolname="UIF::MenuUtils::RenameMenuItemCommand"/>
</thread>
</backtrace>
<registerSet>
<register name="EAX" value="0x00000000"/>
<register name="EBX" value="0x000000fa"/>
<register name="ECX" value="0x50010001"/>
<register name="EDX" value="0x0012ddc0"/>
<register name="ESI" value="0x0c93f3a0"/>
<register name="EDI" value="0x0012df24"/>
<register name="ESP" value="0x00000057"/>
<register name="EBP" value="0x0000004f"/>
<register name="EIP" value="0x00000000"/>
<register name="EFL" value="0x00010246"/>
</registerSet>
<binaryImageSet>
<binaryImage start="0x00400000" end="0x008de000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Adobe Premiere Elements.exe"/>
<binaryImage start="0x7c900000" end="0x7c9b2000" type="__TEXT" path="C:\WINDOWS\system32\ntdll.dll"/>
<binaryImage start="0x7c800000" end="0x7c8f5000" type="__TEXT" path="C:\WINDOWS\system32\kernel32.dll"/>
<binaryImage start="0x10000000" end="0x1000f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\CrashReporter.dll"/>
<binaryImage start="0x59a60000" end="0x59b01000" type="__TEXT" path="C:\WINDOWS\system32\dbghelp.dll"/>
<binaryImage start="0x77c10000" end="0x77c68000" type="__TEXT" path="C:\WINDOWS\system32\msvcrt.dll"/>
<binaryImage start="0x77c00000" end="0x77c08000" type="__TEXT" path="C:\WINDOWS\system32\version.dll"/>
<binaryImage start="0x77dd0000" end="0x77e6b000" type="__TEXT" path="C:\WINDOWS\system32\advapi32.dll"/>
<binaryImage start="0x77e70000" end="0x77f02000" type="__TEXT" path="C:\WINDOWS\system32\rpcrt4.dll"/>
<binaryImage start="0x77fe0000" end="0x77ff1000" type="__TEXT" path="C:\WINDOWS\system32\secur32.dll"/>
<binaryImage start="0x00340000" end="0x0034f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\LogUtils.dll"/>
<binaryImage start="0x7c9c0000" end="0x7d1d6000" type="__TEXT" path="C:\WINDOWS\system32\shell32.dll"/>
<binaryImage start="0x77f10000" end="0x77f58000" type="__TEXT" path="C:\WINDOWS\system32\gdi32.dll"/>
<binaryImage start="0x77d40000" end="0x77dd0000" type="__TEXT" path="C:\WINDOWS\system32\user32.dll"/>
<binaryImage start="0x77f60000" end="0x77fd6000" type="__TEXT" path="C:\WINDOWS\system32\shlwapi.dll"/>
<binaryImage start="0x774e0000" end="0x7761c000" type="__TEXT" path="C:\WINDOWS\system32\ole32.dll"/>
<binaryImage start="0x78130000" end="0x781cb000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.405 3_x-ww_e6967989\msvcr80.dll"/>
<binaryImage start="0x7c420000" end="0x7c4a7000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.405 3_x-ww_e6967989\msvcp80.dll"/>
<binaryImage start="0x77120000" end="0x771ac000" type="__TEXT" path="C:\WINDOWS\system32\oleaut32.dll"/>
<binaryImage start="0x008e0000" end="0x00a34000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dvacore.dll"/>
<binaryImage start="0x00370000" end="0x003fc000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLFoundation.dll"/>
<binaryImage start="0x4ec50000" end="0x4edfb000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.60 01.22319_x-ww_f0b4c2df\GdiPlus.dll"/>
<binaryImage start="0x76bf0000" end="0x76bfb000" type="__TEXT" path="C:\WINDOWS\system32\psapi.dll"/>
<binaryImage start="0x00a50000" end="0x00a56000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PRM.dll"/>
<binaryImage start="0x773d0000" end="0x774d2000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1d f_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll"/>
<binaryImage start="0x012a0000" end="0x012d7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\adobe_caps.dll"/>
<binaryImage start="0x012f0000" end="0x01322000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Startup.dll"/>
<binaryImage start="0x01340000" end="0x01369000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PreRegistration.dll"/>
<binaryImage start="0x01380000" end="0x0168b000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amtlib.dll"/>
<binaryImage start="0x5b860000" end="0x5b8b4000" type="__TEXT" path="C:\WINDOWS\system32\netapi32.dll"/>
<binaryImage start="0x71ab0000" end="0x71ac7000" type="__TEXT" path="C:\WINDOWS\system32\ws2_32.dll"/>
<binaryImage start="0x71aa0000" end="0x71aa8000" type="__TEXT" path="C:\WINDOWS\system32\ws2help.dll"/>
<binaryImage start="0x4d4f0000" end="0x4d548000" type="__TEXT" path="C:\WINDOWS\system32\winhttp.dll"/>
<binaryImage start="0x763b0000" end="0x763f9000" type="__TEXT" path="C:\WINDOWS\system32\comdlg32.dll"/>
<binaryImage start="0x12000000" end="0x121c7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\xerces-c_2_1_0.dll"/>
<binaryImage start="0x016a0000" end="0x016b1000" type="__TEXT" path="C:\WINDOWS\system32\msvcirt.dll"/>
<binaryImage start="0x018c0000" end="0x01dae000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\UIFramework.dll"/>
<binaryImage start="0x016d0000" end="0x01843000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ImageRenderer.dll"/>
<binaryImage start="0x7f840000" end="0x7fa07000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\MCDVD_32.DLL"/>
<binaryImage start="0x76b40000" end="0x76b6d000" type="__TEXT" path="C:\WINDOWS\system32\winmm.dll"/>
<binaryImage start="0x01db0000" end="0x02073000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\libmmd.dll"/>
<binaryImage start="0x02080000" end="0x022ae000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dvaui.dll"/>
<binaryImage start="0x01870000" end="0x01886000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLMessaging.dll"/>
<binaryImage start="0x022b0000" end="0x02ac0000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Backend.dll"/>
<binaryImage start="0x02ac0000" end="0x02c8e000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\xerces-c_2_7.dll"/>
<binaryImage start="0x02ca0000" end="0x02d04000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AudioRenderer.dll"/>
<binaryImage start="0x02d20000" end="0x02d47000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\MediaFoundation.dll"/>
<binaryImage start="0x02d60000" end="0x02d84000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\processcoordinationclient.dll"/>
<binaryImage start="0x02da0000" end="0x02da9000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\processcoordinationsupport.dll"/>
<binaryImage start="0x02dc0000" end="0x02dd3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLUnitTesting.dll"/>
<binaryImage start="0x02df0000" end="0x02e00000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLConsole.dll"/>
<binaryImage start="0x02e10000" end="0x02ed7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dvaworkspace.dll"/>
<binaryImage start="0x76380000" end="0x76385000" type="__TEXT" path="C:\WINDOWS\system32\msimg32.dll"/>
<binaryImage start="0x5ad70000" end="0x5ada8000" type="__TEXT" path="C:\WINDOWS\system32\uxtheme.dll"/>
<binaryImage start="0x02ef0000" end="0x02f19000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\MLFoundation.dll"/>
<binaryImage start="0x02f30000" end="0x02f6f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\About.dll"/>
<binaryImage start="0x031c0000" end="0x03617000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\UIFramework.en_US.DLL"/>
<binaryImage start="0x03630000" end="0x03695000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\About.en_US.DLL"/>
<binaryImage start="0x602d0000" end="0x602e5000" type="__TEXT" path="C:\Program Files\CA\CA Internet Security Suite\CA Anti-Spam\QSP-5.1.18.0\QOEHook.dll"/>
<binaryImage start="0x05820000" end="0x058bd000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amtservices.dll"/>
<binaryImage start="0x77920000" end="0x77a13000" type="__TEXT" path="C:\WINDOWS\system32\setupapi.dll"/>
<binaryImage start="0x77690000" end="0x776b1000" type="__TEXT" path="C:\WINDOWS\system32\ntmarta.dll"/>
<binaryImage start="0x76f60000" end="0x76f8c000" type="__TEXT" path="C:\WINDOWS\system32\wldap32.dll"/>
<binaryImage start="0x71bf0000" end="0x71c03000" type="__TEXT" path="C:\WINDOWS\system32\samlib.dll"/>
<binaryImage start="0x059e0000" end="0x05a00000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\asneu.dll"/>
<binaryImage start="0x05a10000" end="0x0632f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Premiere.dll"/>
<binaryImage start="0x06340000" end="0x065cf000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AMocWrapper.dll"/>
<binaryImage start="0x065d0000" end="0x0660b000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\VideoFrame.dll"/>
<binaryImage start="0x75a70000" end="0x75a91000" type="__TEXT" path="C:\WINDOWS\system32\msvfw32.dll"/>
<binaryImage start="0x06620000" end="0x06627000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\MemoryShell.dll"/>
<binaryImage start="0x06640000" end="0x06654000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\BackendLegacyLib.dll"/>
<binaryImage start="0x06670000" end="0x06677000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Memory.dll"/>
<binaryImage start="0x06690000" end="0x06774000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ImporterHost.dll"/>
<binaryImage start="0x06790000" end="0x067fd000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeXMP.dll"/>
<binaryImage start="0x06810000" end="0x0688f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeXMPFiles.dll"/>
<binaryImage start="0x068a0000" end="0x068a6000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\QTMutex.dll"/>
<binaryImage start="0x068c0000" end="0x068e0000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\MediaUtils.dll"/>
<binaryImage start="0x77be0000" end="0x77bf5000" type="__TEXT" path="C:\WINDOWS\system32\msacm32.dll"/>
<binaryImage start="0x068f0000" end="0x06922000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AudioSupport.dll"/>
<binaryImage start="0x06940000" end="0x06969000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\SweetPeaSupport.dll"/>
<binaryImage start="0x06980000" end="0x069af000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PluginSupport.dll"/>
<binaryImage start="0x71b20000" end="0x71b32000" type="__TEXT" path="C:\WINDOWS\system32\mpr.dll"/>
<binaryImage start="0x069c0000" end="0x06a2d000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ContentAnalysisData.dll"/>
<binaryImage start="0x06a40000" end="0x06a82000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dvatemporalxmp.dll"/>
<binaryImage start="0x06aa0000" end="0x06ab9000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ContentAnalysisDBCache.dll"/>
<binaryImage start="0x06ad0000" end="0x06b07000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ARA.dll"/>
<binaryImage start="0x06b20000" end="0x06b93000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\OLS.dll"/>
<binaryImage start="0x06bb0000" end="0x06bc3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\OperaMgr.dll"/>
<binaryImage start="0x06be0000" end="0x07828000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HSL.dll"/>
<binaryImage start="0x07840000" end="0x07873000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\MediaCoreUI.dll"/>
<binaryImage start="0x07890000" end="0x07918000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dvaeve.dll"/>
<binaryImage start="0x77a80000" end="0x77b14000" type="__TEXT" path="C:\WINDOWS\system32\crypt32.dll"/>
<binaryImage start="0x77b20000" end="0x77b32000" type="__TEXT" path="C:\WINDOWS\system32\msasn1.dll"/>
<binaryImage start="0x07930000" end="0x07a6c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeOwl.dll"/>
<binaryImage start="0x07a80000" end="0x07bc3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\SettingsUI.dll"/>
<binaryImage start="0x07be0000" end="0x07cbc000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\FileInfo.dll"/>
<binaryImage start="0x74c80000" end="0x74cac000" type="__TEXT" path="C:\WINDOWS\system32\oleacc.dll"/>
<binaryImage start="0x76080000" end="0x760e5000" type="__TEXT" path="C:\WINDOWS\system32\msvcp60.dll"/>
<binaryImage start="0x73000000" end="0x73026000" type="__TEXT" path="C:\WINDOWS\system32\winspool.drv"/>
<binaryImage start="0x07cd0000" end="0x07d1a000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\BIB.dll"/>
<binaryImage start="0x07d30000" end="0x07dba000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\EncoderHost.dll"/>
<binaryImage start="0x07dd0000" end="0x07dfe000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PostEncodeHost.dll"/>
<binaryImage start="0x07e10000" end="0x07e48000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amefoundation.dll"/>
<binaryImage start="0x07e60000" end="0x07e8f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ameproperties.dll"/>
<binaryImage start="0x07ea0000" end="0x07f12000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ExporterHost.dll"/>
<binaryImage start="0x07f30000" end="0x08009000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AMEWrapper.dll"/>
<binaryImage start="0x08020000" end="0x080c3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\VideoRenderer.dll"/>
<binaryImage start="0x080e0000" end="0x080f7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AMEAppFoundation.dll"/>
<binaryImage start="0x08110000" end="0x081a2000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\VideoFilterHost.dll"/>
<binaryImage start="0x081c0000" end="0x08295000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\exo.dll"/>
<binaryImage start="0x082b0000" end="0x082ba000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\RoyaltyActivation.dll"/>
<binaryImage start="0x082d0000" end="0x08329000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\RecorderHost.dll"/>
<binaryImage start="0x08340000" end="0x08393000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PlayerHost.dll"/>
<binaryImage start="0x083b0000" end="0x08513000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\DVDCreator.dll"/>
<binaryImage start="0x08530000" end="0x099f2000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AuthorScript.dll"/>
<binaryImage start="0x7c3a0000" end="0x7c41b000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\msvcp71.dll"/>
<binaryImage start="0x7c340000" end="0x7c396000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\msvcr71.dll"/>
<binaryImage start="0x09a00000" end="0x09aba000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\px.dll"/>
<binaryImage start="0x73f10000" end="0x73f6c000" type="__TEXT" path="C:\WINDOWS\system32\dsound.dll"/>
<binaryImage start="0x76780000" end="0x76789000" type="__TEXT" path="C:\WINDOWS\system32\shfolder.dll"/>
<binaryImage start="0x5ed00000" end="0x5edcc000" type="__TEXT" path="C:\WINDOWS\system32\opengl32.dll"/>
<binaryImage start="0x68b20000" end="0x68b40000" type="__TEXT" path="C:\WINDOWS\system32\glu32.dll"/>
<binaryImage start="0x73760000" end="0x737a9000" type="__TEXT" path="C:\WINDOWS\system32\ddraw.dll"/>
<binaryImage start="0x73bc0000" end="0x73bc6000" type="__TEXT" path="C:\WINDOWS\system32\dciman32.dll"/>
<binaryImage start="0x09ad0000" end="0x0a1d9000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Mezzanine.dll"/>
<binaryImage start="0x0a1f0000" end="0x0a202000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ahclient.dll"/>
<binaryImage start="0x771b0000" end="0x77258000" type="__TEXT" path="C:\WINDOWS\system32\wininet.dll"/>
<binaryImage start="0x0a220000" end="0x0a232000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ProjectSupport.dll"/>
<binaryImage start="0x0a250000" end="0x0a2d0000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dynamiclink.dll"/>
<binaryImage start="0x0a2e0000" end="0x0a2fe000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AudioFilterHost.dll"/>
<binaryImage start="0x0a310000" end="0x0a33a000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\DynamicLinkClient.dll"/>
<binaryImage start="0x0a350000" end="0x0a36c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\DVDStructures.dll"/>
<binaryImage start="0x0a380000" end="0x0a4af000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitlerCreator.dll"/>
<binaryImage start="0x0a4c0000" end="0x0a6a7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitleLayer.dll"/>
<binaryImage start="0x0a6c0000" end="0x0a716000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitlerUI.dll"/>
<binaryImage start="0x0a730000" end="0x0a739000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitleOSUtils.dll"/>
<binaryImage start="0x0a750000" end="0x0aa3a000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitleLayout.dll"/>
<binaryImage start="0x0aa50000" end="0x0aaeb000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitleCharacterFactory.dll"/>
<binaryImage start="0x0ab00000" end="0x0abd9000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitleCG.dll"/>
<binaryImage start="0x0abf0000" end="0x0ac33000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AudioFilters.dll"/>
<binaryImage start="0x0ac50000" end="0x0ac62000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ProjectConverterHost.dll"/>
<binaryImage start="0x0ac80000" end="0x0acd1000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ContentAnalysisHost.dll"/>
<binaryImage start="0x0acf0000" end="0x0ad7c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Descriptors.dll"/>
<binaryImage start="0x0ad90000" end="0x0adaf000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\IPLibrary.dll"/>
<binaryImage start="0x0adb0000" end="0x0aee0000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerCapture.dll"/>
<binaryImage start="0x0aef0000" end="0x0b138000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerTimeline.dll"/>
<binaryImage start="0x0b150000" end="0x0b189000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerAudioNarration.dll"/>
<binaryImage start="0x0b1a0000" end="0x0b29f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerAudioMixer.dll"/>
<binaryImage start="0x0b2b0000" end="0x0b340000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerDVDLayout.dll"/>
<binaryImage start="0x0b350000" end="0x0b4cf000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerMonitor.dll"/>
<binaryImage start="0x0b4e0000" end="0x0b526000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PresetManager.dll"/>
<binaryImage start="0x0b540000" end="0x0b68e000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerOrganizer.dll"/>
<binaryImage start="0x0b6a0000" end="0x0b722000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ScCore.dll"/>
<binaryImage start="0x0b740000" end="0x0b7e3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ExtendScript.dll"/>
<binaryImage start="0x0b800000" end="0x0b830000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerHistory.dll"/>
<binaryImage start="0x0b840000" end="0x0b86d000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerInfo.dll"/>
<binaryImage start="0x0b880000" end="0x0b89e000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerEvents.dll"/>
<binaryImage start="0x0b8b0000" end="0x0b8e1000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerSharingCenter.dll"/>
<binaryImage start="0x0b900000" end="0x0b983000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\SCCommon.dll"/>
<binaryImage start="0x0b9a0000" end="0x0bcc0000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerEffectControls.dll"/>
<binaryImage start="0x0bcd0000" end="0x0bd36000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerMovieTheme.dll"/>
<binaryImage start="0x0bd50000" end="0x0c0b6000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerProject.dll"/>
<binaryImage start="0x0c0d0000" end="0x0c0f3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerGetProperties.dll"/>
<binaryImage start="0x0c3d0000" end="0x0c3e1000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\TitlerUI.en_US.DLL"/>
<binaryImage start="0x0c490000" end="0x0c7e7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\Mezzanine.en_US.DLL"/>
<binaryImage start="0x0c410000" end="0x0c448000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\HSL.en_US.DLL"/>
<binaryImage start="0x0c7f0000" end="0x0c864000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\Premiere.en_US.DLL"/>
<binaryImage start="0x0ffd0000" end="0x0fff8000" type="__TEXT" path="C:\WINDOWS\system32\rsaenh.dll"/>
<binaryImage start="0x769c0000" end="0x76a73000" type="__TEXT" path="C:\WINDOWS\system32\userenv.dll"/>
<binaryImage start="0x0cc70000" end="0x0ccdf000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitleFontEngine.dll"/>
<binaryImage start="0x0cce0000" end="0x0ccf2000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\BravoInitializer.dll"/>
<binaryImage start="0x0cd10000" end="0x0ce01000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ACE.dll"/>
<binaryImage start="0x0ce20000" end="0x0d1b1000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AGM.dll"/>
<binaryImage start="0x0d1d0000" end="0x0d47e000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\CoolType.dll"/>
<binaryImage start="0x0e090000" end="0x0e0b2000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitleImageManager.dll"/>
<binaryImage start="0x0f120000" end="0x0f12c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ObjectTracking.dll"/>
<binaryImage start="0x0f140000" end="0x0f15b000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Plug-ins\Common\AsioWdm.dll"/>
<binaryImage start="0x76c30000" end="0x76c5e000" type="__TEXT" path="C:\WINDOWS\system32\wintrust.dll"/>
<binaryImage start="0x76c90000" end="0x76cb8000" type="__TEXT" path="C:\WINDOWS\system32\imagehlp.dll"/>
<binaryImage start="0x72d20000" end="0x72d29000" type="__TEXT" path="C:\WINDOWS\system32\wdmaud.drv"/>
<binaryImage start="0x72d10000" end="0x72d18000" type="__TEXT" path="C:\WINDOWS\system32\msacm32.drv"/>
<binaryImage start="0x77bd0000" end="0x77bd7000" type="__TEXT" path="C:\WINDOWS\system32\midimap.dll"/>
<binaryImage start="0x73ee0000" end="0x73ee4000" type="__TEXT" path="C:\WINDOWS\system32\ksuser.dll"/>
<binaryImage start="0x66800000" end="0x673ab000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTime.qts"/>
<binaryImage start="0x68a40000" end="0x68a6e000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QTCF.dll"/>
<binaryImage start="0x0f3f0000" end="0x0f4ba000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\CoreFoundation.dll"/>
<binaryImage start="0x0f4d0000" end="0x0f4e0000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\pthreadVC2.dll"/>
<binaryImage start="0x71ad0000" end="0x71ad9000" type="__TEXT" path="C:\WINDOWS\system32\wsock32.dll"/>
<binaryImage start="0x0f4e0000" end="0x0f4fc000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\objc.dll"/>
<binaryImage start="0x0f6c0000" end="0x0f7bd000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\icuin40.dll"/>
<binaryImage start="0x0f7c0000" end="0x0f8a1000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\icuuc40.dll"/>
<binaryImage start="0x4ad00000" end="0x4ba5b000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\icudt40.dll"/>
<binaryImage start="0x0f530000" end="0x0f53d000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\ASL.dll"/>
<binaryImage start="0x0f8b0000" end="0x0f943000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\CFNetwork.dll"/>
<binaryImage start="0x0f960000" end="0x0f9c3000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\SQLite3.dll"/>
<binaryImage start="0x0f9e0000" end="0x0f9f3000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\zlib1.dll"/>
<binaryImage start="0x76d60000" end="0x76d79000" type="__TEXT" path="C:\WINDOWS\system32\iphlpapi.dll"/>
<binaryImage start="0x687e0000" end="0x6883a000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\CoreVideo.qtx"/>
<binaryImage start="0x67e40000" end="0x67e9a000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTime3GPP.qtx"/>
<binaryImage start="0x67ea0000" end="0x67f1e000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTime3GPPAuthoring.qtx"/>
<binaryImage start="0x68460000" end="0x687d4000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeAudioSupport.qtx"/>
<binaryImage start="0x67780000" end="0x679ae000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeAuthoring.qtx"/>
<binaryImage start="0x679b0000" end="0x67a03000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeCapture.qtx"/>
<binaryImage start="0x67a10000" end="0x67aa1000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeEffects.qtx"/>
<binaryImage start="0x67cd0000" end="0x67d35000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeEssentials.qtx"/>
<binaryImage start="0x680e0000" end="0x6845b000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeH264.qtx"/>
<binaryImage start="0x67ac0000" end="0x67bb5000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeImage.qtx"/>
<binaryImage start="0x676b0000" end="0x67780000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeInternetExtras.qtx"/>
<binaryImage start="0x67c50000" end="0x67cc9000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeMPEG.qtx"/>
<binaryImage start="0x67d40000" end="0x67d9a000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeMPEG4.qtx"/>
<binaryImage start="0x67da0000" end="0x67e32000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeMPEG4Authoring.qtx"/>
<binaryImage start="0x67bc0000" end="0x67c42000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeMusic.qtx"/>
<binaryImage start="0x673b0000" end="0x6748b000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeStreaming.qtx"/>
<binaryImage start="0x68050000" end="0x680ab000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeStreamingAuthoring.qtx"/>
<binaryImage start="0x680b0000" end="0x680dd000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeStreamingExtras.qtx"/>
<binaryImage start="0x674e0000" end="0x675bb000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeVR.qtx"/>
<binaryImage start="0x58420000" end="0x58427000" type="__TEXT" path="C:\WINDOWS\system32\imaadp32.acm"/>
<binaryImage start="0x72cf0000" end="0x72cf7000" type="__TEXT" path="C:\WINDOWS\system32\msadp32.acm"/>
<binaryImage start="0x58330000" end="0x58335000" type="__TEXT" path="C:\WINDOWS\system32\msg711.acm"/>
<binaryImage start="0x58300000" end="0x58308000" type="__TEXT" path="C:\WINDOWS\system32\msgsm32.acm"/>
<binaryImage start="0x582d0000" end="0x582d4000" type="__TEXT" path="C:\WINDOWS\system32\tssoft32.acm"/>
<binaryImage start="0x73b70000" end="0x73b77000" type="__TEXT" path="C:\WINDOWS\system32\tsd32.dll"/>
<binaryImage start="0x58310000" end="0x5832d000" type="__TEXT" path="C:\WINDOWS\system32\msg723.acm"/>
<binaryImage start="0x58340000" end="0x5838a000" type="__TEXT" path="C:\WINDOWS\system32\msaud32.acm"/>
<binaryImage start="0x582e0000" end="0x582fe000" type="__TEXT" path="C:\WINDOWS\system32\sl_anet.acm"/>
<binaryImage start="0x581a0000" end="0x581d9000" type="__TEXT" path="C:\WINDOWS\system32\iac25_32.ax"/>
<binaryImage start="0x58390000" end="0x5841a000" type="__TEXT" path="C:\WINDOWS\system32\l3codeca.acm"/>
<binaryImage start="0x76fd0000" end="0x7704f000" type="__TEXT" path="C:\WINDOWS\system32\clbcatq.dll"/>
<binaryImage start="0x77050000" end="0x77115000" type="__TEXT" path="C:\WINDOWS\system32\comres.dll"/>
<binaryImage start="0x74980000" end="0x74a94000" type="__TEXT" path="C:\WINDOWS\system32\msxml3.dll"/>
<binaryImage start="0x15ff0000" end="0x16081000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\AppleProResDecoder.qtx"/>
<binaryImage start="0x736b0000" end="0x736b7000" type="__TEXT" path="C:\WINDOWS\system32\msdmo.dll"/>
<binaryImage start="0x74810000" end="0x7497d000" type="__TEXT" path="C:\WINDOWS\system32\quartz.dll"/>
<binaryImage start="0x74ef0000" end="0x74ef8000" type="__TEXT" path="C:\WINDOWS\system32\wbem\wbemprox.dll"/>
<binaryImage start="0x75290000" end="0x752c7000" type="__TEXT" path="C:\WINDOWS\system32\wbem\wbemcomn.dll"/>
<binaryImage start="0x20000000" end="0x202c5000" type="__TEXT" path="C:\WINDOWS\system32\xpsp2res.dll"/>
<binaryImage start="0x74ed0000" end="0x74ede000" type="__TEXT" path="C:\WINDOWS\system32\wbem\wbemsvc.dll"/>
<binaryImage start="0x75690000" end="0x75706000" type="__TEXT" path="C:\WINDOWS\system32\wbem\fastprox.dll"/>
<binaryImage start="0x767a0000" end="0x767b3000" type="__TEXT" path="C:\WINDOWS\system32\ntdsapi.dll"/>
<binaryImage start="0x76f20000" end="0x76f47000" type="__TEXT" path="C:\WINDOWS\system32\dnsapi.dll"/>
<binaryImage start="0x174b0000" end="0x1754c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\MediaIO\codecs\aacaudio.vca"/>
<binaryImage start="0x4f180000" end="0x4f22c000" type="__TEXT" path="C:\WINDOWS\system32\wmadmoe.dll"/>
<binaryImage start="0x17b30000" end="0x17c14000" type="__TEXT" path="C:\WINDOWS\system32\wmspdmoe.dll"/>
<binaryImage start="0x75cf0000" end="0x75d81000" type="__TEXT" path="C:\WINDOWS\system32\mlang.dll"/>
<binaryImage start="0x184f0000" end="0x18602000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ad2h264vout.001"/>
<binaryImage start="0x4c250000" end="0x4c38b000" type="__TEXT" path="C:\WINDOWS\system32\wmvdmoe2.dll"/>
<binaryImage start="0x59090000" end="0x590ae000" type="__TEXT" path="C:\WINDOWS\system32\wmsdmoe.dll"/>
<binaryImage start="0x4ea30000" end="0x4eb87000" type="__TEXT" path="C:\WINDOWS\system32\wmsdmoe2.dll"/>
</binaryImageSet>
</crash>
<reproSteps>
</reproSteps>
</crashreport>

Hello,
I have the exact same problem as you with PE8 and Win7 (x64), and a reboot also helped me. But the problem came back the next time I tried to open PE. Have you expreienced the same? It cant be that we have to reboot every time we want to use PE?
Best regards
Øystein Morvik
Norway

Tracking memory usage

I have run to a memory limitation problem with my MIDP 1 application. So I'm trying to track memory usage. However I found out that WTK memory monitor gives me different results then Runtime memory functions (by calling Runtime.getRuntime().freeMemory()). In particular, Runtime.freeMemory shows less available heap dynamic memory than WTK memory monitor.
How can I then find out what is taking up the memory space that WTK memory monitor hides from me?
Also calling Runtime.freeMemory at the very begining at the start of my application shows me that there is roughly 90KBytes of heap memory in use. What is taking up this space?
Thanks for any hints!
Hynek Cihlar

Of course I did that. I wouldn't have gotten correct results with Runtime.freeMemory if I hadn't done that.
But thanks for the reply ;-).

XML parser memory usage

I try to proove the advantage of SAX (and StAX) parser, i.e. the memory usage over time is very low and quite constant over time while parsing a large XML file.
DOM APIs create a DOM that is stored in the memory and therefore the memory usage is at least the filesize.
To analyse the SAX heap usage over time I used the following source:
import java.io.File;
import java.io.FileInputStream;
import java.io.InputStream;
import org.xml.sax.InputSource;
import org.xml.sax.XMLReader;
import org.xml.sax.helpers.XMLReaderFactory;
public class ParserMemTest {
    public static void main(String[] args) {
        System.out.println("Start");
        try {
            InputStream xmlIS = new FileInputStream(
                    new File("xmlTestFile-0.xml") );
            HeapAnalyser ha = new HeapAnalyser(xmlIS);
            InputSource insource = new InputSource(ha);
            XMLReader SAX2parser = XMLReaderFactory.createXMLReader();
            //SAX2EventHandler handler = new SAX2EventHandler();
            //SAX2parser.setContentHandler(handler);
            SAX2parser.parse(insource);
        } catch (Exception e) {
        System.out.println("Finished.");
}and the HeapAnalyser class:
import java.io.IOException;
import java.io.InputStream;
public class HeapAnalyser extends InputStream {
    private InputStream is = null;
    private int byteCounter = 0;
    private int lastByteCounter = 0;
    private int byteStepLogging = 200000; //bytes between logging times of measurement
    public HeapAnalyser(InputStream is) {
        this.is = is;
    @Override
    public int read() throws IOException {
        int b = is.read();
        if(b!=-1) {
            byteCounter++;
        return b;
    @Override
    public int read(byte b[]) throws IOException {
        int i = is.read(b);
        if(i!=-1) {
            byteCounter += i;
        //LOG
        if ((byteCounter-lastByteCounter)>byteStepLogging) {
            lastByteCounter = byteCounter;
            System.out.println(byteCounter + ": " + getHeapSize() + " bytes.");
        return i;
    @Override
    public int read(byte b[], int off, int len) throws IOException {
        int i = is.read(b, off, len);
        if (i!=-1) {
            byteCounter += i;
        //LOG
        if ((byteCounter-lastByteCounter)>byteStepLogging) {
            lastByteCounter = byteCounter;
            System.out.println(byteCounter + ": " + getHeapSize() + " bytes.");
        return i;
    public static String getHeapSize(){
        Runtime.getRuntime().gc();
        return Long.toString((Runtime.getRuntime().totalMemory() - Runtime.getRuntime().freeMemory())/1000);
}and these are the results:
Start
204728: 1013 bytes.
409415: 1713 bytes.
614073: 2400 bytes.
818763: 3085 bytes.
1023449: 3772 bytes.
1228130: 4458 bytes.
1432802: 5145 bytes.
1637473: 5832 bytes.
1842118: 6519 bytes.
2046789: 7206 bytes.
2251470: 7894 bytes.
2456134: 8580 bytes.
2660814: 9268 bytes.
2865496: 9955 bytes.
3070177: 10625 bytes.
3274775: 11287 bytes.
3479418: 11950 bytes.
3684031: 12612 bytes.
3888695: 13275 bytes.
4093364: 13937 bytes.
4298027: 14600 bytes.
4502694: 15262 bytes.
4707372: 15925 bytes.
4912040: 16586 bytes.
5116662: 17249 bytes.
5321331: 17912 bytes.
5525975: 18574 bytes.
5730640: 19237 bytes.
5935308: 19898 bytes.
Finished.
As you can see while parsing the XML file (200k elements, about 6MB) the heap memory raises. I would expect this result when a DOM API is analysed, but not with SAX .
What could be the reason? The Runtime class measurement, the SAX implementation or what?
thanks!

http://img214.imageshack.us/img214/7277/jprobeparser.jpg
Test with jProbe while parsing the 64MB XML file.
Testsystem: Windows 7 64bit, java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02), Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode), Xerces 2.10.0
Eclipse Console System output:
25818828: 116752 bytes.
26018980: 117948 bytes.
26219154: 99503 bytes.
26419322: 100852 bytes.
26619463: 102275 bytes.
26819642: 103624 bytes.
27019805: 104974 bytes.
27220008: 105649 bytes.
27420115: 106998 bytes.
27620234: 108348 bytes.
27820330: 109697 bytes.
Exception in thread "main" java.lang.OutOfMemoryError: PermGen space
at java.lang.String.intern(Native Method)
at org.apache.xerces.util.SymbolTable$Entry.<init>(Unknown Source)
at org.apache.xerces.util.SymbolTable.addSymbol(Unknown Source)
at org.apache.xerces.impl.XMLEntityScanner.scanQName(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at ParserMemTest.main(ParserMemTest.java:47)<img src="file:///C:/Users/*******/AppData/Local/Temp/moz-screenshot.png" alt="" />
Edited by: SUNMrFlipp on Sep 13, 2010 11:48 AM
Edited by: SUNMrFlipp on Sep 13, 2010 11:50 AM

UCCX 7 Heap Memory Usage Exceeded Error

UCCX 7.0.(1) SR5
Getting the following error when updating or adding new script applications:
"It is not recommended to update the application as Engine heap memory usage exceeded configured threshold. Click OK to continue and Cancel to exit."
Apparently this is an alert that was built into SR4 and is configurable under the System Parameters.
Does anyone have information on what processes use the heap memory in UCCX or how to monitor the usage?

As Tom can attest to by now, this is something of an iceberg with big sharp edges below the surface.
The Java heap is fixed at 256MB on CCX. The Java heap is used by Tomcat as execution memory. In addition to this, applications, scripts, and other repository data is loaded into the heap at runtime. Depending on your environment, you may be approaching the limits of the heap, which cannot be changed. If the heap size is reached, it will be dumped and impact calls.
What have you been doing as of late on your CCX server? How many applications and scripts do you have? Are any of these using XML files extensively?
Note there is also a possible bug where the MIVR engine does not properly release all objects loaded into the heap at the end of a script execution leading to a memory leak of sorts. The discussion [debate] over this behavior is continuing. As of this week, it may be represented under
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
CSCte49231. If it is, this may qualify as the most poorly described defect ever.

Air runtime memory usage

Similar Messages

Maybe you are looking for