Adobe X Memory Utilization Issue - Adobe Please Respond

I have been reading through the forums and have noticed the question come up with no actual resolutions from the Adobe team. I have multiple clients with this same issue, when they open PDF documents, typicaly ones that have been created from a MS Office application (word, excel, powerpoint) or have document security enabled, the memory utilization shoots way up causing system perfomance issues.
The systems that I am working with all are running Windows 7 Pro both 64 Bit and 32 bit, all systems have at least 4+ GB of DDR3 RAM and the latest Intel Core Processors.
I have tried the following to resolve the issue.
Check for and install any available updates.
Uninstall Adobe Reader X and download and install using the latest installer from the Adobe website.
This issue is reporducable accrossed multiple workstations and can be isolated to the Adobe products.
My qustions for Adobe are:
Do you consider this a "Know Issue"
Is this issue scheduled to be resolved in an upcoming update and if so what is the ETA
Are there any current "Work Arrounds"

Hi wayne103,
We released a new security update yesterday that is v10.1.11
Please update to this version and check the performance.
I have seen this error message occur while opening a 3rd party created pdf that has corrupted file structure.
Please let me know if the issue occurs for some specific files or random
Also let me know the PDF producer for these pdfs.
Regards,
Rave

Similar Messages

Datagrid Rendering - Adobe please respond

Please take a look at the example below. If wordWrap=true,
there are cutoffs in the datagrid rendering.
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute">
<mx:Style>
@font-face {
src: local("Calibri");
fontFamily: CalibriEmbedded;
fontWeight: normal;
@font-face {
src: local("Calibri");
fontFamily: CalibriEmbedded;
fontWeight: bold;
Application {
font-family: CalibriEmbedded;
DataGrid {
verticalGridLines: true;
verticalGridLineColor: black;
horizontalGridLines: true;
horizontalGridLineColor: black;
</mx:Style>
<mx:VBox width="100%">
<mx:Panel width="100%" title="wordWrap=true, take a look
at the cutoff at the bottom!">
<mx:DataGrid rowCount="2" width="100%"
wordWrap="true">
<mx:columns>
<mx:DataGridColumn headerText="Column 1"
dataField="col1"/>
<mx:DataGridColumn headerText="Column 2"
dataField="col2"/>
</mx:columns>
</mx:DataGrid>
</mx:Panel>
<mx:Panel width="100%" title="wordWrap=false, looks
ok">
<mx:DataGrid rowCount="2" width="100%"
wordWrap="false">
<mx:columns>
<mx:DataGridColumn headerText="Column 1"
dataField="col1"/>
<mx:DataGridColumn headerText="Column 2"
dataField="col2"/>
</mx:columns>
</mx:DataGrid>
</mx:Panel>
</mx:VBox>
</mx:Application>

This is not an official Adobe support channel. See the
"Important Note:" at the bottom of the page.
Would you be interested in suggestions from non-Adobe folks?
Tracy

16,0,0,240 PROBLEMS???? ADOBE PLEASE RESPOND

I have the latest Flash Player version. However, when I go to my multiplayer golf site, I am no longer able to see my log in information. The site owners advise me to check that I am using the latest Flash Player...which I am. So, why can't I see all the information I am supposed to on my Windows 7 desktop, using Opera browser? It works fine on Maxthon and on IE. It was working on Opera but not any longer. The Flash trouble shooter states that I am ok and that there are no problems with my installation. So what's the problem?

Hi Paul,
The latest version of Flash Player is supported on Opera. Which version of Opera do you have? I'm not familiar with this game and need to investigate. When you say 'some of the information is now missing' what is missing? Please provide steps to reproduce, including expected behaviour and actual behaviour will help in researching the issue.
Also, using Opera browser, please go to Flash Player Help and click on 'Check Now'. What version of Flash Player is detected as being installed?
Maria

Some from Adobe, please respond

I posted this question last week, and have gotten no response from Adobe.
I need to know if the accordion widget works correctly with audio, or if the interface is just incorrect. The audio is not working the way I would expect. Can someone confirm how this is supposed to work?
Logically, when a user selects one of the accordion options, and the option expands to show the text within it, then the associated audio should play. In the image below, you see the audio icon associated with the content for one option. However, in the only documentation I could find, it is very vague about whether the audio is accociated with the content, as indicated, or just with the whole object. Part of this confusion is that apparently you can add audio to a widget in Properties, but that is not what I am doing.
If the audio is just associated with the entire object, then the interface below is incorrect, because it indicates that the audio goes with each option.

You may be working on an older version of the Accordion interaction. Adobe has made frequent updates to these interactions. But perhaps your PC doesn't have the latest versions.
The actual interactions that you see when you open the Select Interaction dialog are the ones located in:
C:\Users\Public\Documents\Adobe\eLearning Assets\Interactions
But there is another backup set stored at:
C:\Program Files\Adobe\Adobe Captivate 7 x64\Gallery\Interactions
It would be nice if someone from Adobe could confirm whether or not Admin permissions to these folders are required in order for the automatic updates to Interactions can occur. If so, that would explain why some users in corporate situations that are not admins might find they are still using older version interactions that still have bugs. When I select one of the interactions in the Public\Documents folder in Win7 it tells me that the own is Administrator. So this tends to indicate perhaps only when an Administrator is logged on can the updates take effect. But I could be wrong.

Setting up; Recording/Playback issues. Please respond

Okay so I'm here to trying to set up Adobe Audition CS 5.5 and I've come across numerous issues here.
For recording I'm using an AKG Perception 220 USB condensor microphone with an Alesis io|2 USB interface.
Audio Hardware Settings.
Device Class: MME (I Have an ASIO option but I'm unsure how to set that up, possibly a link to a guide would help.)
Default Input: Microphone (io|2)
Default Output: Speaker (2-Logitech USB Headset)
Master Clock: Out:Speakers (2- Logitech USB Headset)
Latency: 200ms
Sample Rate 48000
Issues:
-So pretty much when I record I get some sort of lag when I playback. For example if I have someone doing vocals over a beat it will be off by a second, but it was recorded on time.
-Missing Stereo Imagery plugins? Had them before now they're gone?
-Now when i go to record, the track i record vocals over becomes very laggy and distorted; plays slow and there are lots of crackling noises over it.
For use of the ASIO driver to fix these problems do I need an external output device instead of my USB headphones?

There are a few different driver "languages" used for communication between an audio application and the hardware. Audition supports MME, which goes through Windows as a sort of middleman, and ASIO which bypasses Windows and allows the application and device to communicate directly.
MME, which is supported by almost every audio device available, is pretty forgiving when trying to do tasks like use an input from one device with the output of another, or when two applications want to play at the same time. The trade-off for this pliability is an increased latency (it takes longer to do all of this) and unreliability between devices as everythings own internal clock is a little different, causing eventual synchronization issues.
ASIO on the other hand requires the manufacturer of your device to offer drivers. These drivers provide a very specific set of rules for communication, and generally demand complete devotion between an application and the device at any particular time. It's very fast, very accurate, and can generally handle much harder work, but necessitates some strict rules be followed.
If your device doesn't have a true ASIO driver available, you COULD take advantage of a third-party application called ASIO4ALL which provides a means for devices which do not have their own, native ASIO support to communicate with applications that require it. There are also some valid reasons to use it when you want to be able to access multiple devices from within one "shell." (Say, for example, you had two USB Microphones plugged in and wished to record each one to a separate track. ASIO4ALL would allow each microphone to appear as a standard input channel within a single, virtual device. Audition believes it's talking to one audio device called ASIO4ALL, and ASIO4ALL is handling the juggling between the two MME usb microphones and your speakers which might be plugged into a built-in output on your computer.)
If you're able to record and playback and don't experience any problems with your workflow right now, there's no need to install ASIO4ALL and configure it at this point. There is unlikely to be a difference in sound quality, though ASIO4ALL does seem to handle latency a bit better than standard MME drivers.
If it ain't broke right now, I wouldn't recommend trying to fix it.

Adobe, please stop running from this issue! (GPU vs CPU anomalies / fades)

Adobe,
I have tried to bring this issue to light many times, and your own users have argued it ad finem, but to no avail! I am TIRED of getting terrible alpha blending (and opacity curve) results with GPU acceleration enabled, vs CPU. In fact, it is SO BAD that I NEVER work with GPU acceleration any more.
Here is the issue:
When GPU acceleration is enabled, you simply CANNOT do a smooth fade and/or cross dissolve. It appears to fade down smoothly to about 20% opacity, and then the next frame it will jump right to 0% quite abruptly and disappear. It's almost as if the fade simply gives up and switches off! Regardless of whether you use Cross Dissolve, or Film Dissolve the results are the same. Also, your alpha blending is all messed up, CLEARLY showing a different result when comparing CPU and GPU rendering outputs. Once again, this issue ONLY exists with GPU acceleration ENABLED. Switch off GPU/MPE and the problems disappear. But of course you lose the speed and other benefits GPU acceleration offers, which would be great to have! Especially seeing as I have also heard (from various other resources) that GPU acceleration can improve the quality of rendering out to compressed formats like H264. But we will never know that, will we? Because, every time I enable GPU, my fades and blending looks noticeably bad!
I have seen in various other threads that your response has been along the lines of: "That's just the way it is". But unless your name is Bruce Hornsby, this response is unacceptable! You cannot advertise a "great feature" of your products (in this case, GPU/MPE), yet when people try to use it and see odd results, simply tell us: "oh by the way, yeah, it does not work in a few scenarios, like fading, but otherwise you are good to go!" The way I see it: cross-fades (even fades in general) as well as opacity/blending are some of the most common, if not THE most common techniques used in video projects! Having an anomaly of this nature showing a DISTINCT difference in quality output when one of your fantastic "features" is enabled is just poor form. What is evern poorer is your responses (or lack thereof) related to the issue. Especially seeing as this problem has been present since CS5, and now we are STILL seeing it in CC!
Here is a thread which documents the issue well (even shows examples, and other details someone prepared for you to apparently ignore):
http://forums.adobe.com/thread/773441
...it was never addressed there.
Another issue which details it going back as far as CS 5.5:
http://forums.adobe.com/thread/987306
...once again, never resolved.
Now I am using CC, latest version, up-to-date, a fast i7 processor, a CUDA supported card, and all of those go to waste because I have to have GPU and the mercury playback engine disabled to yield decent quality results.
I implore you, not just for myself, but on behalf of everybody here who has already addressed this issue, but has had their pleas fall on deaf ears: PLEASE FIX THIS PROBLEM. Telling us simply that: "This is the way GPU cards choose to render" is NOT ACCEPTABLE. It's just like me saying when I drive my car on the wrong side of the road: "that's just the way I drive!". Doesn't mean it is acceptable!
You may have won people over since Final Cut Pro screwed the pooch with version X... but I can guarantee if this does not get resolved soon, the issue won't just be isolated to the forums here. Expect to read about it in MANY online publications that I am sure your competitors will ENJOY watching!
Mat.

Indeed. Yes Adobe, please explain.
And here is an example of what I am talking about:
CPU only (MPE and GPU DISABLED):
This appears to be what I would consider accurate, as it is not only well blended, but the fades work smoothly thanks to it relying on the CPU...
GPU (MPE and GPU ENABLED - Linear Color ON - as per default):
This provides identical image quality/blending results as the CPU only benchmark. However, the fades are very abrupt, as per the original problem...
GPU (MPE and GPU ENABLED - Linear Color OFF, as per your recommendation):
This is your recommended solution. The fades are as smooth as they are in the CPU version. But as you can see the color, alpha and blending are VASTLY different. Actually, it looks HORRIBLE! The BG text is barely visible, and the foreground text appears to be more prevalent over the top of the back layer, making its fade-up quite disjointed and selective.
...So as you can see, the "solution" you provided seems to create more problems and/or inconsistencies in the overall output. Now we have no idea what is the "standard"!
I personally find these inconsistency's very concerning. And I am sure I'm not the only one. Please tell me there is actually a logic to this "solution" and it wasn't a simple duct-tape fix that nobody there at Adobe actually looked deeper into to see exactly how it would effect overall image quality! It sure appears that way!
I appreciate that you, Kevin, are not directly responsible for this issue, and you are indeed a representative trying to help. But please realize that for many of us here, we are LONG time Premiere users, with years of experience and influence in this industry, and this definitely isn't our first rodeo! When we flag these issues we do so out of a REAL need, which means the consequences Adobe faces as a result of not addressing these issues are equally as REAL! As such; I encourage you to expedite the process of resolving this issue, because it has been prevalent since CS5.5, and the fact that it is not been resolved and/or has been addressed poorly does not bode well for your overall reputation. Especially when you are trying to make Premiere the industry standard. Like I said, I would hate to have to look at alternatives, so give me a solution, because if I decide to move on from using Premiere, I won't be the last. And no, I am not being melodramatic here. If a piece of software cannot seem to get something as simple as fades and blend modes right (or at least CONSISTENT), how can the software be trusted to handle high-end workflows? Food for thought.
Mat.

100% CPU utilization issue by Adobe Form

Hi
I am creating a new Adobe Interactive Form in my web dynpro java application.
When I am trying to run that application on server which is having only 2-3 UI elements in interactive form it's using 100% CPU and adobe form is not getting render.
Some of the adobe forms are already working properly on the server.
Does anybody faced such issue or somebody knows what may cause this issue so please help me out on that.
Thanks
Ravi

Clear CPU Temp folders START->RUN-><Type TEMP> you will get processed Forms that are locally stored in your system Temp folder select all and delete.
and also START->RUN-><Type %TEMP%> and delete the corresponding files in that folder.
Kanagaraja L

Adobe: Please reopen this bug SDK-30917

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

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

Adobe please, fix upload/download speed problems!

Adobe please, before all, fix the upload/download speed issues when updating folios from the computer to the servers and from the servers to the Ipad. It has been so terrible lately.
Thx!
al3nai

Or, better yet, focus on developing great software like you've been doing for years and leave the "cloud" stuff to others. I'd feel a lot better about DPS if I knew I could host it all myself.
Thanks,
Chris

Adobe: Please fix the spacebar cut in multi-camera editing!!

Dear Adobe,
Please fix the BUG which makes a cut in your multi-camera sequence when you hit the spacebar! This is extremely annoying!!
Thanks!
Former FCP User
- Ryan

(imagine the opening of Thriller with the door creaking open and footsteps...you've awoken a sleeping giant...well, not sleeping, recovering actually)
Hi TacoRye.
Welcome to the club. When I saw this post, my eye twitched, my shoulders tensed up and I was brought back to a time (http://forums.adobe.com/message/4714549#4714549) when hitting stop did things that were wrong...just wrong. But as one who's been shut down and locked out of that topic, I'll kindly say that yes, multicam is a bit more enjoyable and free of that design flaw in Premiere CC. In fact, you'll probably like it for a few more things in CC as it's true that they have implemented several FCP favorites in the recent releases that even old schoolers probably say "hmmm, well now this is useful". I was a convert to CS6 from FCP this time last year and open to new things but that stop/pause issue drove me nuts. But it's fixed now in CC. And although I'm dealing with equally frustrating issues in CC on a daily basis unrelated to multcam, unless you use Warp Stabilizer a lot you probably won't experience them. All new software will have its bugs, etc. and I'm still holding out hope that the upcoming release will fix these issues. I have faith. Lots of exciting new features are coming in the next week or so which is all nice and good, but if the actual issues and bugs are fixed, I for one will be even happier.
Bottom line: I encourage you to update to Premiere CC if you do a lot of multicam. Just be sure to update to at least 7.0.1 (the current version as of this post) because the regular 7.0.0 version has a pretty awful multicam bug unrelated to the CS6 thing.
Enjoy...and don't be scared.
(exit with sound of that guy from Thriller laughing...door shuts)

Adobe Please tell what email program will work with my Adobe XI Pro

Office 360 is the worst upgrade or version and I do not want to invest any more time using crappy email I am using Windows 8.1. OK ... Adobe please tell me what high technology email that works with your product. In steady of guessing you must be using something I can use. I am a Professional Engineer here in Michigan developing high tech products. I save email, but I would like to save the structure of my email folders into PDF folders, so I can scan through the emails. I would even printed all 1500 emails if required, but any way I do it using the Office 360's Outlook it errors out to a Help Lync. Blows up. I will write the program, if there is a script language to interface with your product and Microsoft yields information on their OUTLOOK program.
Please tell me what I need to do?
James Wm. Hussey
[email protected]

Hi HuzzCo-USA,
You need to update Acrobat 11 to the latest patch to be able to work with Office 365.
The base version 11.0 is not compatible. From 11.0.1 onwards the compatibility has been added.
Regards,
Rave

Can someone from Adobe please explain why measurements in CS6 are not accurate..PLEASE?

I'm tired of wasting my time looking for reasons why measurements I key in are constantly changed to some arbitary number decided by Illustrator. I'm currently working on a 100mm x 100mm box with a corresponding grid and yet for some reason my measurements get changed to 100.238mm or 99.834mm or similar... I just wasted another 10 minutes trying to work out how to ask someone this question...am I the only one experiencing this...NO! Any answers Adobe, please?

The above answers are absolutely correct, because it was obvious @Brayhill had Pixel-Snap turned on.
Specifically for print work, where keying in values may sometimes not show correctly* in the Control Bar at the top, there is another little hidden setting in Preferences -> General -> Use Preview Bounds.
If you are doing millimeter perfect templates for example, and want the total to show for example 100 x 100mm, regardless of the stroke weight asigned, just uncheck the Preview Bounds box in Preferences.
*Checked will always add your stroke width (as well as some other effects) to the total shown in the Control Bar. This can also be very useful at times, say when you need to fit an entire group with strokes and effects within 100x100mm, like an advertisement.

Adobe - please explain how to soft proof in LR2

I have read all the messages I could find. It seems clear that LR2 has no soft proofing of my prints. And yes, I am working with a color managed screen.
So Adobe, please tell us how you intend us to soft proof our images????

>Really? "most professionals do not calibrate their monitors." I find that unbeleavable.
Me too, but I know a few working pros that simply trust their expensive monitor is good enough. Weirdly some of them will spend a long time obsessing over color (typically skin tones) but don't bother to calibrate. This just boggles my mind. Seems to work for them fine though.
>I will agree that I am getting amazing prints out of LR2
Color is great for me too. However, I identified a major, reproducible on multiple machines, resolution bug with LR 2's print module at least in the OS X version and am curious if others see it too, especially on windows.
Jao, "Loss of Sharpness Printing Actual Size from Lightroom" #15, 24 Aug 2008 11:22 pm
In short. I. Printing at native resolution by unchecking "print resolution" does not work. LR2 will still scale but to the value now shown in light grey. II. In rotated images (like a portrait format RAW on a portrait paper) LR2 calculates the resolution to send to the printer based on the wrong dimension, resulting in a far lower resolution sent to the printer than specified. LR 1.4 does not have these bugs. This also impacts the print to jpeg feature and makes the Print module in LR 2 basically useless for me as I can only trust it to do the right thing in a limited set of circumstances.

I have paid for a year subscription, but all the PDF's I attempt to export to Word give me a "Conversion Error" message, citing that the "file's security settings do not allow export." I want a refund. Adobe, please advise. Thank you.

I have paid for a year subscription, but all the PDF's I attempt to export to Word give me a "Conversion Error" message, citing that the "file's security settings do not allow export." I want a refund. Adobe, please advise. Thank you.

Hi la recruiter,
There are a few types of files that Acrobat can't convert--and PDF files with security applied is one on them. I'm happy to cancel your subscription, if you decide that it's not going to work out for you. Please confirm that you'd like me to proceed with the cancelation, and I'll take care of it right away.
Best,
Sara

Feature Request: Adobe, please make After effects CC keyboard shortcuts customizable as in Premiere

I'm making this feature requests because I've tried the only two known methods for customizing keyboard shortcuts in After Affects and neither of these work in CC:
• 2008 video tutorial on Creative Cow Forum for modifying the After Effects Keyboard shortcuts text file - unfortunately this doesn't work in AE CC
• a youtube tutorial about how to install KeyedUp for After Effects - tried this but also not able to change any shortcuts in AE CC
One of the things I love most about Premiere Pro CC is how many keyboard shortcuts you can customize. You can even do this in Adobe Audition.
So why not in After Effects?
Adobe please bring this feature to the next update of After Effects CC.

Hi Todd,
Sorry I replied to you in the Creative Cow forum. Just in case you didn't see my reply there, I'm reposting it here:
Essentially after following the tutorial video very carefully, modifying the shortcuts, making sure there are no traces of other instances of the old shortcut, I save the file then when I reopen AE, I get this window:
Then when I check the folder housing the shortcuts text file I see that my modified shortcut text file simply got renamed "old" at the end of the line:
See second line in window "Shortcuts.txt.old" -> that's the file I modified. It looks like AE simply spawned a new default shortcuts file titled "...Shortcuts.txt"

Adobe X Memory Utilization Issue - Adobe Please Respond

Similar Messages

Maybe you are looking for