Storyline Update 5 Crashes on Apple iPad - Fails Sumtotal LMS

Jul 22, 2014

We have chosen Storyline as a enterprise tool for Content development for Mobile Apple iOS and hosting in SumTotal 2013 as a LMS, we are publishing the courses as AICC and Publishing for iPad safari as a HTML5 output.


When Loaded in the LMS the LMS is Launching the Course as Expected and from the Launch tab the course is launched on a Separate Tab when the user completes the course and closes the course the storyline content is causing a Safari Crash( Not a Visual Crash but Causes a Huge memory load and Other tabs are getting refreshed ) Causing hte Sumtotal Window to Fail resolving to the Launch Flow and Sumtotal Indicated that it is the Storyline that is causing the crash.


Sumtotal Case #[Case #00549076] – [Abbvie Inc] – [Priority 1] – [LMS]


Crash reports from Safari when this crash happens

Response from SumTotal on this Issue

- Articulate Story line had some limitations with course size, Number of slides in the course, Number of video/audio clips in the course. Please review the following articles which talks about the issues with HTML 5 content with IPAD's

As a next step we would like you perform following steps and we will discuss more about it in tomorrow's call.

- Create courses with lesser slides (Slide count:20) and validate the issue after clearing the cache.

- Upload the courses to Articulate Test site and validate outside LMS to confirm the issue is with Articulate.

- Engage Articulate support to review the High CPU usage issue and see if they can release the fix for this issue. We would like to participate in your discussion with Articulate support and provide necessary assistance.

PRODUCT: Articulate Storyline

3 Replies
Ashley Terwilliger-Pollard

Hi Sembian and welcome to Heroes,

Thank you for sharing that information here and I'm sorry to hear that this is an issue you continue to experience. I see that you're also working on a support case with Regil (Case number # 00411220 for my reference). I will follow along in your case with Regil, as I see he shared that it has been reported to our Quality Assurance team for their review although we cannot offer a timeline for when the issue will be resolved.

If you need anything else, feel free to let Regil or I know.

Sembian Balasubramanian

Hi Ashley,

It is very frustrating that I am not able to resolve or get a solid answer from Support, This is the response.

Thank you for pointing this out.

I have forwarded all the information you provided to our Quality Assurance Team. Unfortunately we do not have a timeline on when this can be resolved.

I will however, inform you immediately whenever I get any update on this.


Is is a bug or not so we can move forward, is there a approved workaround for this issue ?


Christine Hendrickson

Hi Sembian,

I apologize for any confusion. Yes, if our Quality Assurance team is investigating the issue, it is considered a bug.

The support case that was assigned to your issue was provided in the ticket with our QA team. I'm also adding this thread, so we can share any updates here as well.

Please make sure you're subscribed to this thread, as well as any other community members that run into this issue, and we'll be sure to let you know as soon as we have more information on this issue.

I do apologize for the trouble. Hopefully we'll have more information on this soon!



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