Low on Memory?! Cant save!

I'm having this issue too (and have a deadline today!). Have there been a resolution to this? Please please say Yes!

Not very helpful input coming up (sorry!) just a point of curiousity, I have been given to work on, a super powerful laptop, 2.3 ghz processor (dual core quad logic proc) 2gb ram (yes the super powerful bit was sarcasm), I regularly run multiple story's alongside photoshop, captivate, flash pro and even run podcasts/youtube etc and apart from being a touch slow, never experience software problems. 

Again sorry that isn't actually helpful but everyone here seems to be running big machines - time to downgrade! 

Also probably stupid question but could the fact that the machine is running 64 bit and AS is running 32 bit be causing any issues?

Hi all,

having serious memory issues here. I am on v5 and have a 16bit Windows 2008 server with 16GB memory. We have changed to this as the laptop of similar spec just couldn't hack the project I am building...

It is struggling with saves and loads on larger files. I have noticed though that when the Physical Memory (Cached) reaches the same as the total & available it just gives up! (this is in Task Manager under the performance tab)

The Free is down in the 100's.

It seems that I have to restart to clear the Cache and then AS is better behaved...any thoughts, ideas, help? Our IT guys are going slightly bonkers!!!!!

Yes, I'm still having memory problems that preclude saving a project file in Storyline. I have a project that ideally would include 46 or more scenes. I've had to break the project into three projects. Each scene is composed of approximately 10-12 slides. If I get in the 15-16 scene range, I have no guarantee that the project will save after making corrections/changes/additions. I have routinely published the project (someone told me once that that would reduce the size of the file and reduce the chances of it not saving). I have the latest version of Storyline installed (Update 4) and am running on a i7-2600 3.4 GHz system with 8 GB of RAM. I wish it were not the case, but the issues have not disappeared with Update 4.

Hi Thomas,

Update 4 did fix  the issue where "Available Memory Is Low" warning would appear when opening player properties. Have you tested update 4 yet for your courses? Also, I'm not aware of future plans for 64-bit support, but you're welcome to submit a feature request. 

I would be interested to find out if anybody is still experiencing these issues? We are building a HUGE course for a client. 70+ scenes hitting around 694 MB and for the majority of the build we didn't experience the memory error until the course hit 60+ scenes. Now it simply won;t let us save the file effectively halting development entirely.

Have these memory issues been further addressed in the release of version 4? It bowls me over that this happens on a machine with 16GB of RAM. I hope there are plans to bring Storyline up to a 64-bit platform so it can really take advantage of some big memory! It's a great piece of software being currently held back.

Hi Frederic, 

It sounds like you've tested out a number of the above options to troubleshoot, so at this time I think the next step would be for you to submit a Support case and then our team can test your files. 

Thanks!

I still have memory issues that corrupt my .story files.

When it happens, (even if the file is local), I can't open the player configuration tab, and can't save. Any publication fails. 

I know that importing the currupted storyline in a new storyline project resolve this... Until it happens again later. 

I'm losing a lot of time... May the articulate team resolve this, please ? This bug is critical, and deserves an update. 

I don't want another solution to fix my filesmyself, I just need that my files never get corrupted. 

Storyline is an expensive software. And it's still bugged as it was still in a beta test. 

Sorry, running out of patience...

Please, I need solutions about this...

At least, a post with a list of things of "don't do this" things to make this bug never happen again.    

Thank you.

Hi Brad,

Sure thing! 

I'm glad to hear this isn't affecting all of the projects. Out of curiosity, are there any big differences between the one having issues and the ones that are working properly? Maybe size of the project?

Also, you might want to make sure you're working with the project locally:

• Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior. 
• You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
• Avoid using special characters, accents or symbols in your file names (this includes spaces and underscores).

Additional information regarding "Naming Files, Paths, and Namespaces" in Windows operating systems can be found in the following Microsoft article.

Thanks!

Hi Christine,

I checked a few of my files that I created before the update, and they appear to be working correctly.  Thanks for your quick response!