Memory not being released

Hi All,

something strange is happening with my computer's memory.

When I start SL and load my project, it takes about 400MB (yes, its a large project)

I make some modifications and save the project (memory usage approx 420 MB)

When I publish it, the memory usage creeps up to 1.1GB.

If then publish it again, mind you I do not make any changes, I just republish it, the memory usage doesn't start from 420MB, as I expected it to be, no it starts at 1.1GB. After it has crept up to 1.6GB, the publication either just stops and renders the publish window, or SL just disappears...

It is like if the allocated memory isn't purged when no longer needed

Worse is that when I publish and then make more modifications, as the memory is not freed, I run against a not enough memory to save the project issue.

I opened a case with the helpdesk. They are the best, nevertheless they could not simulate the issue

Has anybody experienced something similar

Thanks

Geert

21 Replies
Jeff C

Hi Geert, I've noticed the memory not being released on occasions. Once after I got the low memory warning I deleted everything and the memory usage stayed the same. I could not save a project with one slide in it due to low memory. 

I think the problem is that when you start pushing the memory limits of SL corruption can occur to SL data or your project and anything can happen after that. 

I'm just breaking up my project into several parts now to get around the issues we both seem to be having.

Mark Kizilos

I have had this same issue as well.  It got considerably better when I installed the first update to storyline, but it still is a problem. I wish I could break my project into parts, but I have a number of modules that share data, and I can't find another way to pass variables from one module to the next that works across iPad and flash versions.  Unfortunately, I may be bumping against the limits of the program...even when I am able to publish a file, it is no guarantee that I will be able to publish it a second time. I find myself having to restart over and over --take one step  forward and then end up taking two steps back. The end results has been weeks of frustration. And my file has gotten so complex that I can't imagine anyone from articulate will be able to take the time to troubleshoot this with me. 

Peter Anderson

Hey guys, 

Sorry to hear you're experiencing these issues. It sounds like Geert has already opened a case on this (thanks!), but I'd encourage others to open tickets on it as well. The files may be complex and we may not be able to replicate the behavior, but the more we learn about it, the better we'll be able to hep prevent it in future updates. So please, if you haven't already, go ahead and send us your files so we can take a closer look at what might be causing this. Thanks a ton!

Kristine Stollar

Hi, I do have an open ticket and am experiencing the same issues. This issue is killing me personally, and causing awful delays on a project.  I think that ultimately we are pushing this application beyond its limits. Can I ask a stupid question that may have nothing to do with anything..why isn't SL a 64-bit application?

Mark Kizilos

Kristine: I have not fully resolved this.  I monitor the resources by pulling up task manager and if things start to get too big, I save, exit and restart.  I had the same thought about 64-bit...frankly I was stunned when I learned that it is not 64-bit.  This memory issue is a huge and problematic limitation. If you can parse your project into smaller components, then it is manageable, but if you can't, then you are stuck.  As I mentioned, though, the first (and only) update made things much better, and I am able to work much longer before having a problem. 

Right now my biggest issues are that Articulate-online seems to be very finnicky for publishing.  I publish a file once with no problem, and then try the next day with the same file and I get an "unknown error"--repeatedly. But I have posted that elsewhere

The saying about love-hate relationships is starting to sum up my experience with Storyline. It is amazing when it is working...I guess we early adopters have to work out some of the bugs:) 

Jesse Spinella

I'm having those issues as well. I had a very large file reach 94mb and it won't let me preview, publish or save any more, had to split it up. But that's not what the company I work for wants. The individual modules need  to be apart of one single file.

It's a large file that's only half done, and at this point I'm not sure at this point if SL will allow it to be completed. Fortunately they aren't asking me to complete that project yet, so its not an issue (yet) but it will be in the future.

Are there fixes in progress to address these issues?

tom riddle
I am having the same problem.  I just opened a ticket and uploaded the file.   This is the second occourance.  The first time I removed a few scenes that were essentially duplicates.
Storyline is a good product and nuciance (sp?)  bugs will happen with any product as fully featured as Storyline is but loosing data is a show stopper.    Work cannot be lost.   
 I was able to do a bit of a workaround by selecting/copying groups of slides from scenes into a new project.   This worked pretty well when I selected and copied a range of slides from a scene, less so when I tried to copy a entire scene.  In the later case audio was messed up. (showed the audio name on the slide timeline  but couldn't see the waveform.  When clicking on it, it did open up the sound editor, but it froze, requiring an alt+ctrl+del to kill the ap
I tried closing other open apps but that didn't help.  Then went into task manager and killed some non-related processes, but that didn't help either.  
Peter Anderson

Hi Dave, 

Currently, Storyline is a 32-bit application, which means Windows only allows us to address 2GB of memory.This is something our guys are working on improving for the future. In the meantime, here are some suggestions that may help:

1.  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.  
  
2. 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). 
3.  Avoid using special characters, accents or symbols in your file names. 
  
Additional information regarding "Naming Files, Paths, and Namespaces" in 
Windows operating systems can be found in the following Microsoft article: 
http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx 

================ 

And you can delete Articulate temporary files:

** It is sometimes helpful to delete all files and folders from the temp 
folder and not just the Articulate folder. Ask your IT department for 
assistance with this if you are unsure how to proceed. 

1) Close all running applications. 
2) Open Windows Explorer and go to %temp%\Articulate 
3) Select all files and then the press the Delete key. 

** You may skip any files you are not allowed to delete. We only need to 
clear out your temp folder as it can affect your system performance if the 
temp folder is getting full. 

Jesse Spinella

Not supported by Articulate, but this has worked for me: http://www.ntcore.com/4gb_patch.php

If you have a 64bit os, and at least 8gb of memory on your machine, you can use this patch to increase the virtual memory SL uses. It's not endorsed by Articulate, but it works great. Seriously cut back the errors I get when running SL. I still get a memory problem here and there, but not to the extent I used to. Maybe once a month as opposed to once, sometimes twice a day.

The program is free, website is virus free and it's 3rd party solution, but it really works.