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

Hi Maciej,

Storyline 360 is a 32-bit application and Windows limits 32-bit applications to only use 2GB of RAM.

However in your case, it seems that the memory consumption is indeed quite too high for the size of your project.

Also ensure that your are saving the project on your local drive. Working on a mapped network drive or a USB drive can cause resource conflicts and the inability to save or publish.

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?)

Having the same problems here too, I try to save as regularly as I can but I still end up getting the low memory error and having to force close storyline and lose a few hours of work.

Seems a bit daft that Articulate don't offer a 64 bit version by now?

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! 

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?

Yuppp, just tried that file out and i'm getting the same issues straight away.

That was ridiculously slow.