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.

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.

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.

hi Folks, thanks for all the tips! My case is finally resolved, and I found the root cause of the 'low memory' error message, file is in use error, slowness of the program, and various program crashes, due to the project file have TONS of slide masters within it. When working with the support team, he mentioned about having the file in a 'new file'. This triggered something for me, as in the case with both of my project files that were giving me troubles, they had both been old presenter files that had been imported to SL2 and then SL3, and now SL360 - well all those slide masters came with it. I had applied a 'bIank'/clean slide master to all the slides, but those masters still remain even though they aren't used. I eventually ended up having to copy in just text, images and audio into a brand new SL360 file so no slide master layouts came in - once I did this, no issues of the low memory error, file is in use error, or program crashes or slowness. I tried to delete the slide masters from my original working file, but it would just crash on me so given my tight deadline, I couldn't waste anymore time and just found it faster to copy and paste what I needed into a new file...... even though these projects are both approx. 200 slides (+/-). I had multiple copies of both my project files from doing 'save as' because I would get the 'file in use' message. I lost hours of work and changes because I never knew if my file would save. I had gone to my IT support and had them install more RAM on my computer and was working off my C: drive - I had turned off the auto-save feature to stop SL from creating tons of huge zip files. Articulate support had provided some uninstall/reinstall steps, I had just installed 360 so didn't feel that was necessary and/or part of the issue. So it took me some investigating but finally determined it was those darn slide masters!!! There were hundreds of slide master layouts - it was unbelievable!! So, my advice if you run into this issue, check your file for slide masters!!!!!! and/or start with a new file. I hope this can help others who run into this issue!!

Hi Kristi, Great news! We just released another update for Articulate 360! The item you'll be interested in is how our new browser-based sign-in experience fixes an issue where the Articulate 360 desktop app was blank or unresponsive for people using the latest Intel processors with built-in Iris Xe graphics. You can read about the update here. Just launch the Articulate 360 desktop app on your computer and click the Update button for each application. Details here. Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.

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

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

EswarkumarKanth
Community Member
3 years ago
Please give me the solution for this. I am also facing this issue.
- ToddBearson-236
  Community Member
  3 years ago
  This just happened to me again. I had to leave the computer alone for a
  bit (40 mins) to do something else. When I came back, it worked. FWIW,
  right before it happened, I was putting a large file up on Review 360.
  - EswarkumarKanth
    Community Member
    3 years ago
    Thanks for the replay. Is it working after some time?
EricaMcCaig-36e
Community Member
3 years ago
I am also running into this issue...thanks for any guidance.
- Clara_Suntinger
  Staff
  3 years ago
  Hello Erica,
  
  There are a few things you could try:
  
  Make sure you are following these tips
  
  If your project is large, consider breaking it up into smaller modules. This not only helps with your performance while authoring, but will help with performance if the course is hosted on the web or an LMS
  
  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.
- leilafariddanes
  Community Member
  3 years ago
  When I installed theses updates the issue solved : KB5013942, KB5013624, KB4023057.
leilafariddanes
Community Member
3 years ago
Hi,

I was constantly getting memory low errors and lose work too. I took a long time to solve this problem and I would like to share it with you. I had this problem with my new laptop 32GB, intel core i7, 64bit and with original Win 10. And YES, it was a windows issue. The problem is that windows don't let you install any .net framwork in your computer and say that you have the last one, but the version of .net framwork did not work well. So when I installed theses updates the issue solved : KB5013942, KB5013624, KB4023057.

I hope neither of you experience this tedious problem.
AndreaKoehntop-
Community Member
3 years ago
Hello Andre, and welcome to the E-Learning Heroes community! ✨

I apologize for the issues you are experiencing with the low memory error in Storyline.

Here are some best practices for reducing your risk of corrupting or losing project files.

I want to ask you a couple of questions to begin troubleshooting:

Does this happen in every .story file when you try to publish your course, or one particular file?

How big is the file you are trying to publish? You can try breaking it up into smaller modules. This not only helps with your performance while authoring, but will help with performance if the course is hosted on the web or an LMS

If this error is happening with one file in particular and the measures above don't seem to help, you can feel free to share your .story file with us publicly here or privately in a case so our support engineers can investigate further. We will delete it from our systems when troubleshooting is complete.
RHoisan
Community Member
3 years ago
Hi, this memory error happens to me as well very often lately. I now have a brand new PC with Windows 11 installed, 16RAM...Please investigate compatibility with Windows 11, I never had these issues on my Laptop or older PC with Windows 10.

This happens across projects, with various random actions like creating a new trigger or inserting an image...I get a big red X on the screen and I can't save.

I am doing all the right things since I work with SL since v1...

Thanks.

edit: just found that this could be related to an issue affecting newer Intel 11th gen processors which is what I have.
https://articulate.com/support/article/Storyline-Memory-Leaks-When-Using-Machines-With-Intel-Iris-Xe-Graphics

I have nVidia graphics but it seems to be a processor compatibility issue with 11th gen ones. And the fact that SL is a 32-bit app does not help. Please fix this as it makes work for some of us literally impossible (unless we downgrade our machines!).
MariaCS
Staff
3 years ago
Hi, Robert.

Thank you for reaching out!

I want to connect you with one of our support engineers to investigate if it could be related to the processor since you mentioned having an NVIDIA graphics card instead. I opened a case on your behalf, and you should hear from our team soon via e-mail.
- RHoisan
  Community Member
  3 years ago
  Thanks, Maria.
  
  So what I did was change the project thumbnail yesterday as described in the link above AND also I had an idea to enable compatibility mode for SL. Right-click on the SL icon, choose properties and enable compatibility for Windows 8. I am not sure if any of these did anything, but some good news I had no errors for the past 24h. We'll see if it lasts...I will let this know in the ticket as well.
  
  Robert
AllisonNowak
Community Member
3 years ago
I've been getting a similar problem, even 4 years later. I'm getting a "Project file could not be saved" message with the ApiCode of [E_OUTOFMEMORY/Out of memory].

Not sure why this would be happening since my computer's memory is nowhere near at full capacity.

Sometimes when I reboot, the problem goes away, but them I'm losing the last 20 minutes or so of work.
- EswarkumarKanth
  Community Member
  3 years ago
  Hi,
  
  I hope if you follow the mentioned step in your system it will help you for resolving the issue.
  
  https://community.articulate.com/discussions/articulate-storyline/errors-when-i-save-the-file-in-storyline360#reply-783226
Maria-VictoriaB
Community Member
9 months ago
This problem is still happening :(
- StephenV
  Community Member
  9 months ago
  It must be because we're not paying enough every year for this program to work as expected. Good thing they're raising the price by another $100 per year! /s
- StevenBenassi
  Staff
  9 months ago
  Hi Maria!
  
  Sorry to hear you've also run into this setback!
  
  To confirm, are you authoring in the 32-bit or 64-bit version of Storyline 360? Also, are you receiving any error messages when your project fails to save? If you are, it would be helpful to see a screenshot of the message, as well as the .story file that's giving you trouble.
  
  Feel free to share those here in the discussion or privately through a support case. Looking forward to hearing from you!