Low on memory error even after Update 2

Mar 05, 2013

I thought the can't-save-because-low-on-memory issue was resolved in Update 2, but I'm running into the problem again.

I'm on an XP machine (3 gigs of memory), so I can't use the patch that was suggested earlier. I've got a bare minimum of stuff running in the background and close everything I can from the task manager, but I still can't save. I've restarted my system, cleaned out the recycle bin, and am storing files locally. My files are neither big nor complicated (about 9,000 kb and <50 slides).

It seems that memory is not being released. What happened this morning was this: I had a question bank with 20 slides. I wanted to duplicate the last slide 20 times (for a total of 40) and then make minor changes adjusting the question on each of the new slides. It didn't let me save, and eventually I just had to abort. I tried again, this time watching what was going on in the Task Manager every time I duplicated the last slide. What happened was that the memory usage would climb dramatically up to about 1 million k pretty quickly. However, I discovered that if I made just 2-3 copies of a slide, saved as a new name, and got completely out of Storyline, I could reload everything, and the memory usage would be reasonable. I just had to keep doing that. Closing the file wasn't enough. I had to get out of Storyline each time for the memory to be released. It's just very time consuming to keep doing that.

Is anyone else having low memory problems even after Update 2? Any new suggestions or words from the technical folks at Storyline? I stopped working on Storyline last fall because of the issue, and I've just recently returned to it. It's a nasty shock to see the old problem resurface.

Thanks,

Dorothy

2 Replies
Christine Hendrickson

Hi Dorothy,

Thanks for all of the information. I'm very sorry to hear that you're running into this issue. 

If you haven't already, please try to follow the troubleshooting steps outlined in the following article: 

Articulate Support > Unexpected behavior in Storyline

If you see no change after following those steps, please co ahead and submit a support case with our support team:

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.

This discussion is closed. You can start a new discussion or contact Articulate Support.