Low on Memory?! Cant save!

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

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. 

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

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. 

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.

Hi Mary,

How big is the course? Can you share it here with us so that we can take a look? If you're unable to post here in the forums, I can send you directions on how to share with me privately or your always welcome to connect with our Support engineers.

It didn't work. I downloaded the new version of SL, rebooted, went to republish my course and after it got 3/4 of the way through, it popped up the Publish window. Ugh. Please help! This course is set to launch to 1,000s of employees...

Thanks. I've downloaded the update. Fingers crossed!

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. 

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