Low on Memory?! Cant save!

Hi Dana,

First, can you tell me what version of Storyline you're using, please? To find this information, click on "Help" and "About Articulate Storyline".

If you're not running version 3 (1305.2012), please download and install the update using the link below:

Articulate - Storyline Update 3

Once you've finished installing the update, please republish and test your course on the iPad. If the problem continues after installing the update, or if you already have Update 3 installed, please let me know.

Thanks very much!

Christine

I am having a similar issue.  If I return to a file I created, I cannot publish, make changes to the player or even preview the whole project.  I get a Low Memory error and to close other programs.  I installed updated earlier this week and the issues appear to be happening since the update.

Thoughts?

Hi Brad,

Sorry for the trouble. Are you able to open and work with any other files, or does this seem to be affecting all projects you open or create?

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!

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!

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

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.