Help: Available Memory Is Low Error Appearing Since Update 2

Opps... I meant Update 3.  Sorry

Hi Blake!

Have you tried restarting the machine when you receive this message? Does that help? 

Also, you mentioned importing solves the issue temporarily. Can you tell me if this happens for one specific file, or does it happen with multiple projects?

If this happens with multiple projects, it might be something we need to investigate. Please go ahead and contact our support team so we can take a closer look at what may be happening on the system:

Articulate Support - Submit a Support Case

Please be sure to include a description of your issue. Please also include the URL for this thread in the form. Also, please share the case number with me. You're welcome to do so here, or in a private message. This way I can follow the progress of the case and update this thread.

Thanks!

Has any resolution come to this issue? I too am experiencing the same thing. The issue with the Memory is Low pop up only happens when I try to open the Player options, after that the program becomes unresponsive. If I try to preview a project it hangs at around 90% regardless of the size of the project and if I try to publish it will go through the motions and look like it publishes but there are no files outputted to the publish folder.

I have been training my department on using Articulate and created a sample project prior to the last update and all is good with that file, now when I try to recreate the exact same project using the same files about 5-6 slides into the project I begin getting these errors every time.

I have now just recently started working on a real project for my department, 12 slides with heavy content and 6 question slides so far and just started getting the errors on this file as well. Need help!

Thanks Blake for bringing up the option of just copying all the slides to a new project, hopefully that will get me back up for now since I have a tight deadline on this project but really need some resolution into this issue for the future.

Hi James,

Did importing the slides into a new project file help with the memory error? 

Also, can you confirm you're working with local project files as well, please?

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

I haven't had any luck finding a support case for Blake yet, but this was only posted yesterday. 

If you have the chance, please go ahead and contact support with the details you shared here. Also, if you can share some information with us about your system (operating system, RAM, etc.) that would help a lot as well.

Thank you!

Sorry for the delayed response... I have been super busy.

I think I have another solution... Before I was opening a second instance of Storyline and copying and pasting the slides.  This was a temporary fix as the problem continued to occur.  Christine mentioned importing the *.story into a new *.story.  I tried this, and it was much easier and more efficient than copying and pasting the scenes/slides.  But, the problem still occurred.  The preview would never complete and when I clicked on the Player button to edit the skin, I got the error again.  

So I followed these instructions.

After I did this, I realized that this erased ALL of my previously saved Player Skins.  So, I tried to open my original file and open the player skin that was saved to the file, and I got the error again.  This made me think that maybe my file is not corrupted, but maybe it is the player skin. 

So, I imported my original *.story into a new file, and then rebuilt the Player Skin to the specifications that I wanted, and I am happy to say that this seems to have fixed my problem.  Since I did this, I have had no errors.  

Thank you.

Hi Blake,

That's great to hear! So sorry you had to put so much work into this, but I'm very pleased that you were able to find the cause and get this working. 

Thanks for sharing this information as well, this could come in handy for other community members that run into the same error.

I hope you have a wonderful Friday, Blake!

Christine

I just had the same exact issue as described by James Castoro. I am working on my local hard drive and haven't done anything out of the ordinary with filenames, etc... I rebooted, but even after rebooting when I opened my story (that had been working fine before), I couldn't preview the project, and when I tried to publish it left out all of the html files. If I tried to look at the Player, it gave me the low memory error. Makes me think the Player can get corrupted. I was able to import it into a new storyline file.

Hi Will,

Sorry to hear that you had the same problem! Is everything working ok now that you importing it into a new file? If not just let us know. 

I just started experiencing this exact error today. Seems as though somehow the player files can become corrupted, rendering the .story useless and requiring you to create a new player. Problem is, if you don't have documented every single little thing you changed in the player design (all colors, every state, every line, etc.) then you are stuck having to start from scratch and pray that you remember it all. That renders the ability to import new player designs into existing lessons useless.

Seems like an issue the tech team needs to get onto... this will become old very fast.

I too am receiving this error, which only started to occur this week, but is a serious problem. I read somewhere that the problem might be linked to the logo file, however, I cannot remove it from the player since I can no longer open the player in those files; each time I try I get the memory error. I have uploaded 9 files that I am having problems with in hopes that it will help lead to a link to the problem and a solution. In the mean time I will use a different logo file and rebuild the player. Thanks for the suggestion.

I just received a response back from Articulate and it appears the problem is caused by abad logo image.The logo image I used was not bad originally, but became bad over time/use, so it appears that Storyline does something to the logo file in the player over multiple uses. The only current fix seems to be to send the files to Articulate and have them remove the logo from the .story file.

From time to time I get the very same message. I solve that by simply saving the story with another name through the "save as" feature.
I don't know why, but it works!
It generally happens with big .story files.

Hope that helps!

Thanks Mauro and Deb for your updates, and as Deb mentioned if you'd like to share you files with our Support team you can send them to us here. 

Hi folks

Hope this is the right place to mention this. I've been having this trouble when clicking the Player button. There is a page here that describes a logo issue causing this: http://www.articulate.com/support/kb_article.php?product=st1&id=8kvns29ijgpb 

I'm under time pressure, so just wanted to point out something of a "quick-fix".

We had a logo in our template, but in some projects were not using it. Having built a course, I wanted to get into the Player to adjust the menu. When I hit Player, I was getting the system memory message. I found the above page, and thinking the problem might be our logo:

1 Created a new project

2 Applied the (same) template

3 Before doing *anything* - Went into the player options, turned "on" the logo, then deleted it (when the logo is there, but not in use, it is "faded out", and has to be turned on before it can be deleted)

4 Back on the actual (empty) slides; went into the "Design" tab and added the theme for the project that we had created

4 Imported the previous ("problem") project.

All is now fine. Also - my formatting has all come through as well. 

I hope this might help anyone who is under a bit of time pressure in resolving or getting around the issue. 

Hi Brendan,

Thanks so much for sharing it here, and you're definitely in the right place! Glad you figured out a fix.