Forum Discussion
storyline 360 can't save my project (low memory error)
Hello,
I'm working on some project. I have done 5-4 slides. Sudenly SL360 starts to work very, very, very slow (almost can't do anything in it). I can't even save my project. It's happening to me few times already after working with one file for 3-4 hours. I'm sending screenshots from two errors (I'm getting those when I try to save my project). I have 32 GB of ram, so it's not a problem. I'm working on windows 10 64bit.
My slides contain: 4 photos, 15-20 buttons, 15-20 text files, few shape objects, 10-15 layers with one audio.
edit: SL360 starts working slower gradually.
When I reopen my file, it's all good and program takes only 400MB from memory. I think taht problems start when it's reaching ~3GB of RAM.
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.
- JihongJinCommunity Member
Hi,
We ran into this issue as well in 360.
One thing I want to get better understanding: it mentioned in one of the posts above: 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.
Does it mean SL2 supports 4 GB RAM and SL360 only supports 2 GB RAM? If this is the case, I don't understand why Articulate does not make SL360 also supports 4GB RAM, since both SL2 and SL360 are 32 bit app?
Thank you very much, and I am looking forward to hearing from you soon!
Hi Jihong,
Great question.
The same is true for SL360 as well, so no worries there.
Now, you ran into an issue saving your project?
Ashley shared an update above, which you can read here, about some corrections being done in Update 14.
So, I'd be sure to update to the latest, which is now Update 15.
Please feel free to share your .story file and the details of the error with our team here if you're still having difficulty as we certainly want to take a look at any other performance issues.
- JihongJinCommunity Member
Thank you very much, Leslie, I will let the team know to update to the most recent version.
If we run into this issue again, I will let you know.
- KennethHam-9315Community Member
Add me to the pile. Running the most current version, saving locally, & the only other applications running at this time are required business processes (background) and chrome. Task Manager says the current memory allocation for Storyline360 process is ~400MB. Total system memory allocation for all applications, including SL360 is 2.6GB.
When I try to "Save As..." it says it can't save due to parent stream being disconnected. When I try to save, it says low memory error and/or parent container closed.
I have to present the review draft of my project in a little less than 2.5 hours and my best hope at this point is publishing to CD and screen sharing. However, I will have to redo all of the work I've done this morning after I present it, as I assume everything will be lost if I close this instance of Storyline360.
I've also tried to share to team slides, in hopes that I could recover that way, but still got an error, so that wasn't an option. - JihongJinCommunity Member
Hi Leslie,
With the most recent update of SL 360 installed (v3.15.15581.0), one of my co-workers still ran into the cannot save issue with the error message mentioning low memory. What I don't understand is that, when cannot save happens:
1) Save to another location may work, for example, instead of saving locally, saving it to a network server. However if continue the change and save to the same location, it cannot save again
2) Save to a different file may workIf there is really a memory issue, saving to another location or saving to a different file SL 360 should require the same amount of memory, right? Does the SL 360 report the accurate error message?
And regarding what Ken mentioned about losing work, just wonder if the auto recovery copy will be available for this case (to be found in ...\AppData\...) although the user have to choose Don't Save. If not, I think we really need it.
Thank you!
Hi Jihong,
If you're on the most recent update and still seeing the low memory error, I'd want to have you work directly with our team to look into what is happening on your end. The team is still working on overall performance issues, so it'd be helpful to have more examples of this. Can you reach out to them here and they'll provide you next steps?
The auto recovery should only take effect if Storyline crashed or otherwise closed out of the application and file. It also requires one initial save of the project.
- TinaWilksCommunity Member
Any update on this SL360 issue. I just started witht eh free trial four days ago. My file is only 40MB and now when I try and swap a couple of character poses I get the low memory warning and the file won't save.
I assume as I only started with this product a couple of days ago i must have the latest version.
I'm a long time Captivate user - and have been impressed enough with Storyline to try it but I'm having serious doubts - which is a shame cos it is a real nice auhtoring tool when it behaves - but as a contractor I can't afford to mess around svaing every few minutes and risking losing the whole porject
- RossPriluker-41Community Member
Hi Tina,
Yes, I know it can be frustrating. I've experienced this as well. However with these errors and glitches, my personal opinion is that Storyline is still much better than Captivate. Our company has used Captivate in the past and from our experience, it was even more glitchy than Storyline. Whenever I get the low memory error, sometimes what works is instead of trying to save it, hit "save as" and name is as a different file. It can be something as simple as your original file name with the number 2 after it. This sometimes works for me. Also, try typing in the search bar on your pc "%temp%" and go into this folder and delete everything. Don't worry, none of your saved work will be deleted, these are just temporary files that take up memory. Another thing you can try is in Storyline, go to File --> Storyline options --> and uncheck the "Save AutoRecovery information every 10 minutes". This may help limit the number of temp files that are being created, which can take up space. Although this is not a complete fix, which I feel Articulate should be more thoroughly looking into; these are some workarounds I've found helpful in the past, hopefully they will work for some of you.
- TinaWilksCommunity Member
Thanks so much Ross
I do the 'save as' and using v1, v2 etc anyway - have had issues in the
past with other software where the file you just keep saving gets corrupted.And I will definitely try the other things you suggest
Thanks, Tina and Ross, for sharing here. Our team is still investigating reports of the low memory error. We've released an update in April which has eliminated this issue for lots of users, but if you're still seeing this message, we'd love to help.
Tina, if you're still getting stuck, can you share your experience with our support engineers? We'll explore some specifics with you and see if we can find a good resolution. Thanks!
- FelipeVilleg485Community Member
It is extremely frustrating that this issue has not been resolved. I have lost hours and hours of work.