Low on Memory?! Cant save!

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

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?

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

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

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. 

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

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

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.

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