Low on Memory?! Cant save!

Got this message when saving:

The project file could not be saved.

Your system appears to be low on memory. Please close any other programs and try again.

I have 12GB RAM, 3GB used 8GB Free!

What should I do, don't want to redo that whole section again...

My project is 108 slides comprising of lots of quiz questions, 8 sections

116 Replies
Christine Hendrickson

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!

Frederic Chaplin

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.

Thomas Stembridge

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.

Jonathan Bacon

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.

Eric Brennan-Hazell

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!!!!!

Alex O'Byrne

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?

Jannicke Wilhelmsen

I had the same issue, I am running on Windows 7 - 64 bit. After looking around the forum for answers I found one telling about a 4gb patch. If you are running on 64 bit this can maybe help you. It is not from Articulate, but it patches x86 executables in order to let them have 4GB (instead of only 2) of virtual memory on x64 platforms. This has solved my problem. You find the patch on this link: http://www.ntcore.com/4gb_patch.php

Hope it can help you

Ashley Terwilliger-Pollard

Hi all,

Since the last post in December, we've also now released update 5. If you're using an earlier update I'd suggest downloading update 5 and try publishing using that version. You should be ok using the 64 bit version of Windows as indicated here in the system requirements, and you'll also want to confirm that you're working with local project files and publishing to a local drive. 

EJ LeBlanc

I experienced this same issue and received the same message, but, because I believed it had nothing to do with RAM (I have 24GB), I checked my hard drives. My new laptop came with a partitioned SSD that only had around 100GB allocated to the boot/Windows drive. 

I used WinDirStat to see why my hard drive kept running out of space, as I had been very careful to only install the apps necessary to run the machine and should have had plenty of room on the drive to conduct normal operations. Additionally, I was always saving my work and working from another drive entirely, so it didn't make sense why I was losing space. 

WinDirStat revealed my C:\Users\UserName\AppData\Local\Temp\Articulate\Storyline\ folder was the culprit. The only way I could fix this was by removing the other partitioned drive and expanding C drive to take over its space. I have not had an issue since, although I had to delete and reinstall Storyline during this process. However, I will say I just cleared this temp folder, and I already have another 7GB of temporary storage consumed by it on my SSD. 

Believe Storyline 2.0 should provide users with control over where they want their cache and temp files to be stored, much like Adobe offers in CC programs.

Ashley Terwilliger-Pollard

Hi EJ,

I'm sorry to hear that you experienced the odd behavior as well, and thanks for sharing the steps you went through. I also wanted to remind you that Storyline files should be saved and published to your local drive as described here.  

Also in regards to Storyline 2.0, your suggestion would be something I'd also recommend sharing in the form of a feature request as those go to our produce development team. 

Jim Momsen

Hi Ashley,

I have the "Cannot Save - Low on Memory Issue" in SL 2. The project is currently one (Very Large) video from which I was going to create separate View and Try Scenes. I have never saved the Story, so I don't want to shut down and lose everything. Is there a way to save?

Thanks again,

Jim Momsen, CPT

Ashley Terwilliger-Pollard

Hi Jim,

Are you using the latest update of Storyline 2, update 4?  I know that fixed a lot of issues that users had with saving files - but you may also want to look into if your temp directory is full. Here's how to empty it:

  1. Open Windows Explorer, type %temp% in the address field, and press Enter.
  2. When your temp directory opens, press Ctrl+A to select all the temp files, then press the Delete key on your keyboard.
  3. A few temp files may currently be in use that can't be deleted. When prompted, you can skip those.
  4. You can now save your project file.

Please also find the download for update 4 here if you don't already have it. 

Jim Momsen

Hi Ashley,

Looks like I'm at Update 3.

Due to the prior Admistrator issue that you helped with (thanks again), I'm logged in to Storyline under her ID and cannot delete Temp files in her user space. She just left for the day. I'll give it a try when we can switch users and she can log in under her ID to clear out the temp files in her space.

Worst case is that I'll need to exit Storyline and re-record the scenario (after installing Update 4, of course).

Regards and thanks again,

Jim Momsen, CPT