Articulate Storyline Error Report - Publish couldn't complete successfully

Jan 06, 2020

Hi Team,
    I am developing the carcass file using a storyline 360. The files contain a lot of GIF animation. While taking output by publishing, an error occurred and it related to memory allocation failed. How to resolve this issue? Could you please provide the solution as soon as possible ?.

I have attached the error popup and error information text file.

7 Replies
Katie Riggio

Hi there, Janagiraman. So sorry you hit that error during publish!

For our first steps, let's see if a fresh installation of Storyline 360 helps.

If the course continues to crash after, would you be willing to share the .story file with us for testing? You can share it privately by using this upload link. We'll delete it after taking a thorough look!

Leslie McKerchie

Hi Jeannette,

Thanks for reaching out and sharing that you're running into a similar issue and the troubleshooting that you've already done.

I responded to a similar post here, but it seems that you've narrowed it down a bit more.

It sounds like you may have a corrupt object or slide in this project file. I'd recommend the following to narrow it down a bit more:

  • previewing individual scenes to narrow it down
  • previewing individual slides in the scene 
  • once the problematic slide(s) are identified, you can hide items on the timeline and preview until you identify the problematic items on the slide

If you need our help, then with your permission, please share your project file. You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.

Ren Gomez

Hi Tony,

We received your reply that you received an incorrect email. Just as an FYI, you're subscribed to this conversation, which means you'll get an email for any reply that comes up afterward.

If you'd like to unsubscribe, feel free to scroll to the top of the conversation and select the Unsubscribe button. I hope this helps clear up any confusion!

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