Constant Crashing - FRUSTRATING!

Oct 24, 2018

The platform has been crashing on me between 3-5 times a day over the last week. I've been working on a complex training module with numerous layers and content within each layer. I understand that the design is complex, but was expecting the software to be able to handle the workload. I keep getting the "Memory is Low" error. I actually increased my memory from 8GB to 16GB for this reason, and should have the machine power and performance to do what I need to do. I've started saving often, but I shouldn't have to deal with the system crashing numerous times a day and getting the "We're sorry, what were you doing when it crashed? We appreciate your feedback..." message. Nothing is being done about it. What do I need to do?

8 Replies
Susi B

Hi James,

are you working locally or on a network? > Working locally is recommended. In the past I had to work on a network and I had similar problems, when the file got too big, so I changed to working on my desktop and save backups at the end of the day on the network.

If you are already working locally, does this happen every time you are doing the same thing? Like changing the layout, clicking a specific button? > Sometime when the files get too big and you duplicate a lot ot slides, the file can get corrupt. Even a single slide can get corrupt and can cause this issue.

You could also send your file and a little report when this happens to the support so they can have a look into it.

Regards

Susi

Leslie McKerchie

Hi James,

Thanks for reaching out and sharing what you are experiencing. That certainly is not the behavior we want you to have.

I'm glad to see that Susi was able to pop in and offer some insight based on her previous experience.

I see that you did reach out to our support team and Renz has sent you some troubleshooting as well.

Just let him know if you continue to have difficulty after that and we will continue to work with you.

Leslie McKerchie

Hey Dany,

To elaborate on 'working locally':

You should always save and publish all of your Articulate Storyline files and projects to your local hard drive, which is typically your C: drive. Working on a network drive or an external (USB) drive can cause erratic behavior due to latency, which is the amount of time it takes for the information to traverse the systems. As a result, your files might become corrupted, you could be unable to save changes, or your application might “freeze” altogether.

Follow These Tips to Reduce Your Risk of Corrupting or Losing Project Files

Curious if the issue happens in any course you are working on or just this particular one?

If you cannot re-create the issue in a new course, I would advise to import the file into a new one and proceed.

If it's happening in any/all files, you should conduct a repair of your software.

This discussion is closed. You can start a new discussion or contact Articulate Support.