Adobe Community : All Content - All Communities

Too much RAM consumption in Photoshop CC 2014.

forums_noreply@adobe.com — Thu, 23 Oct 2014 08:00:37 GMT

Hi people,

Since the update to Photoshop CC 2014 I'm having serious problems with the amount of RAM used by Photoshop.

When opening a file (only) 245 MB big, Photoshop uses around 3.5 GB of RAM. As a result my PC is extremely slow.

This was never the case in previous versions. Files made in previous versions are now hard to work on in the CC 2014 version.

Some bigger files are now useless. It takes forever to open them and impossible to work on because of this RAM issue.

I can not open other apps or even browsers at the same time anymore, because Photoshop consumes too much RAM.

Is it normal Photoshop uses 3.5 GB RAM while the file is that small?

When comparing with other Adobe (CC 2014) software only Photoshop uses that amount of RAM.

If you look here http://helpx.adobe.com/photoshop/system-requirements.html#Photoshop CC 2014 system requirements and language versions

you can see the minimum requirements of RAM:

Photoshop CS5: 1GB

Photoshop CS6: 1GB

Photoshop CC: 1GB

Photoshop CC 2014: 2GB (8 GB recommended)

OK, new versions need more RAM, I understand. But in my case it seems like 6 GB is not enough.

And I have the feeling even 8 GB won't be enough too.

Can someone please tell me if there's a problem with Photoshop CC 2014, will this be solved?

Or is this normal behaviour, and should I buy more RAM?

Buying more RAM is of course the easiest answer to solve this.

But don't you think the jump from 1 GB to (minimum) 8 GB RAM is very big?

And like I said, I don't think 8 GB will cover it too. Then how much will be enough?

Thnx in advance!

I have:

OS: Windows 7 Pro

Processor: Intel Xeon CPU W3550 @ 3.07 GHz 3.06 GHz

System Type: 64 Bit PC

RAM: 6 GB RAM

Available Disk Space: 283 GB

Kind regards,

Lester.

Code Panel In Edge.

forums_noreply@adobe.com — Wed, 17 Sep 2014 08:59:55 GMT

Hi,

Does anybody knows a way to expand/collapse all folders together (on the left side) in Edge's code panel easily?

When having multiple files opened and you have to switch between them, all folders get expanded automatically every single time you switch.

If you have quite a lot of symbols in 1 file, you also have a very long list with expanded folders.

In this case I find it better to just expand the ones I need at that moment without having to scroll like crazy.

I see this as a bug or not finished.
Wouldn't it be better (or normal) that Edge remembers the state of the codepanels when switching between files?

And maybe the possibility to add a shortcut for expanding/collapsing all at once?

I find Edge Animate super, only the codepanel may be a bit more advanced.

I come from a Flash background and I still miss simple features like "Search & replace" and "Pin active script".

This would be a HUGE timesaver at least for me when developing in Edge.

Kind regards,

Lester.

Render symbols (or images) with display set "cache as bitmap" possible?

forums_noreply@adobe.com — Mon, 24 Mar 2014 12:29:06 GMT

Hi people,

A question;

I have like 12 symbols on the stage. They al have images in them in JPG format, saved at a quite low percentage in quality.

The symbols are being animated seperately but it looks very sluggish.

I am recreating a whole Flash site in Edge. Everything works (amazing) fine except I am missing the function like it exists in Flash:

“Display/ Render/ cache as bitmap”. (see image)
This function used to help me BIGTIME in Flash too.

Now how can I do something similar in Edge?

I do not want to animate all symbols as 1, it is essential they are animated separately.
Is this possible in Adobe Edge Animate? Is there something similar in Javascript/ Jquery?

Thnx in advance!

Lester.

Get the ID of a dynamically created symbol from library, INSIDE another symbol.

forums_noreply@adobe.com — Sat, 08 Feb 2014 10:43:38 GMT

Hi everyone,

I'm trying to get the id from a dynamic created symbol from library.

When dynamically creating the symbol directly on the stage (or composition level), there's no problem.

But I just can't get it to work when creating the symbol inside another symbol.

Below some examples using both "getChildSymbols()" and "aSymbolInstances"

// USING "getChildSymbols()" /////////////////////////////////////////////////////////////////////////

// ON THE STAGE

var m_item = sym.createChildSymbol("m_item","Stage");

var symbolChildren = sym.getChildSymbols();

console.log(symbolChildren[0].getSymbolElement().attr('id')); // ok eid_1391853893203

// INSIDE ANOTHER SYMBOL

var m_item = sym.createChildSymbol("m_item", sym.getSymbol("holder").getSymbolElement());

var symbolChildren = sym.getSymbol("holder").getChildSymbols(); // Am i using this wrong maybe?

console.log(symbolChildren.length) // returns 0 so can't get no ID either

// USING "aSymbolInstances"" //////////////////////////////////////////////////////////////////////////

// ON THE STAGE

var m_item = sym.createChildSymbol("m_item","Stage");

console.log(sym.aSymbolInstances[0]); // ok (i guess) x.fn.x.init[1] 0: div#eid_1391854141436

// INSIDE ANOTHER SYMBOL

var m_item = sym.createChildSymbol("m_item", sym.getSymbol("holder").getSymbolElement());

console.log(sym.getSymbol("holder").aSymbolInstances[0]); // Javascript error in event handler! Event Type = element

In this post http://forums.adobe.com/message/5691824 is written: "mySym.aSymbolInstances will give you an array with all "names" when you create symbols"

Could it be this only works on the stage/ composition level only and not inside a symbol?

The following methods to achieve the same are indeed possible, but i simply DON'T want to use them in this case:

1) Storing a reference of the created symbol in an array and call it later by index.

2) Giving the items an ID manually on creation and use document.getElementById() afterwards.

I can't believe this isn't possible. I am probably missing something here.

Forgive me I am a newbie using Adobe Edge!
I really hope someone can help me out here.

Anyway, thnx in advance people!

Kind Regards,

Lester.