Forum Discussion
Storyline is constantly crashing
I'm getting the error "Your system appears to be low on memory". My computer has tons of free memory though. I have no idea what the problem is but it's been happening for as long as I've had this new Dell PC. Am i the only one having this issue?
I have to save after every keystroke in fear of a crash.
the errors are all documented in the log files
open in windows file explorer
%LocalAppData%/Articulate/360/Logs/
-> Storyline_STABLE_yyyymmdd_hhmmss.log
send these files to articulate (or upload them here)
if there is a pattern - it can be find (this is no secret science)
JürgenThanks, Jurgen. This was so helpful! I couldn't run through the steps exactly as you mentioned, but I mentioned it to the Articulate folks working on my ticket and they walked me through the process and identified my issue from the logs.
Hi Mat!
Sorry you ran into this issue. I went ahead and created support case 03227750 on your behalf so our support engineers can take a closer look at your installation. Your case is in good hands, and a member of our support team will be in touch with you shortly!
I also have this issue. I literally click Save after every add/edit/delete because the whole thing crashes every 5 minutes. It's happened for months and with multiple different .story files.
Hello Havaleh!
I'm happy to help! It looks like Mat's files were saving to OneDrive which was causing the frequent crashing and error message. Are you saving projects to an external or shared drive like OneDrive, Dropbox, etc?
If so, I'd recommend saving your files locally like to a Documents folder or another folder saved to your local drive which is typically your C: Drive.
If that doesn't do the trick, please let me know!
Months ago, I saw that this was a known issue for quite some time. So, I saved all new .story files to my Desktop. Unfortunately, the problem persists.
That's exactly what I did but then found out my desktop folder was on OneDrive. IT set up my computer like that for some reason.
Never mind, Storyline is still crashing a lot for me.
Hi mat!
Sorry to hear that Storyline is still crashing after ensuring you save to your local drive rather than OneDrive! Is it all courses or just one course where you're noticing Storyline is frequently crashing? Also, have you tried repairing Storyline 360?
I am experiencing the same. Storyline is constantly closing after a few changes/edits. Saving my files locally. Already tried to re-install the desktop software but it keeps going on. It also doesn't give any error-messages or something like that.
Hello Bureau E-Learning & Simulation Training MOC (DL),
Since you are not getting any error messages whenever your Storyline 360 installation closes, I'd first start with doing a repair of your Storyline 360 installation to see if this helps. If the issue persists, you can reach out to our support team by opening a case so we can take a closer look at your installation to figure out what's happening.
I am experiencing the same. Storyline is constantly closing after a few changes/edits. Even while saving my files locally, still it showing low memory, but we have enough space.
PC Configuration:
Processor: Threadripper 3990x
RAM: 64 GB
Storage SSD: 500GB
Storyline version: June 21, 2022 - 3.65.28121.0
Please help me out.Hello Niveditha!
Thanks for sharing a screenshot with us! Have you tried a repair of Storyline 360 as well? If that doesn't do the trick, I'd recommend connecting with our Support Engineers by submitting a support case.
I have the same issues! I get "not enough memory" pop-ups and crashes multiple times a day! I have followed all advice I could find in this community forum platform. Still, the problem persists.
Thanks Jurgen. Can you or someone from articulate explain these steps in more detail? This is indeed "secret science" for me.
I opened a ticket and I mentioned Jurgen's suggestion, they provided me with steps and it led to identifying the exact issue - which was my graphics card: Intel(R) Iris(R) Xe Graphics, in simple terms, they are junk and while there are proposed solutions, nothing fixes the issue.
