storyline 360 can't save my project (low memory error)

I'm working on local drive.
Its soooooooo frustrating when I have to restart program after some edit/create objects jobs. When I'm not restarting SL360 its getting slower and slower and bugs start to appear like: when you try to select multiple groups then sudennly some groups are moving 100 pixels to left or just elements in those groups getting smaller or bigger or moving where they want.

This program have some serious memory problem (leak?)

Hi Maciej and James, 

Storyline 2 is a 32-bit application.  More specifically:

• Storyline 2 is Large-Address Aware, which means that it can access up to 4 GB RAM rather than the default limit of 2 GB for a 32-bit process.
• Storyline 2 does not explicitly take advantage of multiple processor cores at this time, although we continue to focus on performance improvements for future updates.

If you're running into performance issues with Storyline 360, specifically the "available memory is low" error, our Support team is hoping to find additional examples and information of what could be causing this error by working with individuals one on one. Can you reach out to them here? 

Thanks, James - any insight or info you can offer will be helpful as we continue to track down the cause of this! 

HI Ashley 

I've been working on a project file for the past two weeks and it was only yesterday I got this message half a dozen times over a few hours.  I was saving after every few slides so I didn't lose much as I had a deadline yesterday. File size is 84MB.

I know there is a SL360 update I need to install but I am still running SL360 v3.12.14647.0 as I don't like to upgrade mid project (I've been caught out before).

I'm always working on the latest version of SL360.
Now I'm just saving a lot and restart program after finish every slide.
I started to look into task menager (windows) from time to time and when it's close to 2GB (memory), I restart program too.

When SL360 starts working very slow I restart it too.

I can echo the same issues as the others. I am using SL360 on one of our engineering systems with an Xeon processor, 32 GB of RAM and a 500GB hard drive. All my projects are on my local drive until complete, when I then place them on the network drive for storage.

This seemed to have started about ten days to two weeks ago when there was an update to SL360. I have several video clips in the project and the file size is about 3GB. 

My IT section ha ruled out any hardware issues. Are you working on a solution? What is the timeline?

I would like to share SL360 killing slide :(
How I supposed to work in that kind of environment?

That was ridiculously slow.

Hi Wendy, Mark, and James,

I'm sorry you've hit this too. 😕

It's really important to us that we make progress on this performance problem.  We're working hard to nail down reproducible scenarios, and we still need your help.

If you haven't done so already, please send us .story project files that demonstrate the problem, and/or Peek videos that show us how to make it happen.  AND, if you can please share your Case Number in this forum thread after doing so, I'll make sure it's connected to this discussion so our team is aware of the steps you've already tried.

Thanks! 

It's hard to reproduce Ashley as it is so inconsistent.  I didn't find it happening when I did any specific action - sorry I can't be more help but good luck tracking it down :-)

Thanks, Wendy - I know one of my colleagues was reviewing all the comments here and any open cases for users, so they may reach out to you as well! 

Thanks Ashley, Victor reached out with a number of best practices - all of which I am already following.

I completed the project I was working on and have since upgraded to latest version 3.13.15006 and haven't experienced the issue so far - so fingers crossed.

I just hit this error for the first time.  I am using version 3.13.15006 of SL 360.  Thank goodness I am a habitual saver, but I did lose about 20 minutes of work.

Brant

I have with the latest update. 

Hi Nancy and Brant,

I'm sorry this has plagued you too. Our team is chasing these performance issues down, and we could use your help! Can you connect with our Support Engineers here and let me know once you do, I'll make sure it gets to the right team. 

We'll keep everyone posted here as we continue to investigate!  

Interesting - I haven't had it with the latest update but the new file I'm working on at the moment is under 20MB.  I, like a lot of others, are manually saving after every few slides though.

We're having the same problems before and after the latest update - very frustrating!  We are using macbooks which makes it more difficult as we struggle with windows anyway! Please make articulate for mac. Again cant send peek as seems to be random.

Hi Miranda - Could you connect with our team here as Ashley shared above.

Just got it again with the latest update. 

Action: I had made a copy of a file and was trying to delete scenes.

The only other app open was Chrome.

I'm saving after every few actions so while it's an inconvenience I'm managing around it.

Hope they solve it soon :-)

Hey Miranda,

Thanks for reaching out to our support team. We are trying to pinpoint what's going on with user files :)

Hey Wendy,

I see that you shared an example with the support team and I added your latest action steps to your case as we continue to track this issue.

Thank you!

Ok, so memory leak is fixed (hope so). What about low performance, lagging issue of SL360 (and all other versions of storyline i guess) which I introduced earlier? 

Hi Maciej,

Correct, Update 14 resolved a memory leak which accounts for errors folks were seeing that said things like "Available Memory is Low". You'll see this noted in the release notes for Storyline 360 as:

Fixed: Storyline could become sluggish or display a low memory error, especially after several hours of use. We found a memory leak and fixed the problem. We're so sorry for the frustration it caused. And thank you to everyone who reported it!

We still have an open issue for the performance issues that our team is working on, so we'll let you know as soon as that is resolved too.

I've been having the same problem for about a year and still no fix. Articulate promised the latest update back in March would fix the issue and it's still a problem. I've searched every forum and tried every solution and nothing works. There's forums dating back 6 years with the same exact issue. I am so frustrated right now! I work for a big marketing corporation and I can't get any work done with this bug. I've tried the whole, empty your %temp% folder thing and also emptying the  %appdata%\Articulate\Storyline  folder.... repeatedly. I can't save any work. I'm forced to start a new project in a separate window and copy the slides I worked on into that project, save it, and then restart my computer and copy those slides into the main project. And before you suggest creating a new project and importing all the slides....yes I have done that as well...problem still persists. I've aslso uninstalled and re-installed Storyline 3 repeatedly as well. This is absurd! You guys really need to get with the program and fix this issue. Storyline is unusable. I got deadlines to meet with these modules and I can't make them because this issue continues to slow me down. Don't refer me to other forums that you "claim" fixes the issue, because it doesn't. Believe me I've checked. And before you ask, "yes" all my files are local to my hard drive, I am not working off of a USB or External. I'm sick of this "low on memory" error, and "project can't be saved at this time" annoyance! Why don't we have 64 bit support yet? Also, I am running a top of the line macbook pro with VMware fusion and I have my virtual memory all the way up. No dice! I literally had to repeat the above so-called "solution" 30 times today! I can't keep doing this! I can continue to write a novel here but I think I'm finished expressing my frustration! Why my company is even spending their money on this software is beyond me at this point. It seems whenever you need to create a basic module it's fine...but then when you begin creating more heavy-duty modules, Storyline can't handle it. Please fix, and don't take 6 years to do it! Btw, I'm using the latest version of Storyline 3.