Storyline - Memory Leak with iPad Safari

Aug 22, 2013

Storyline has a memory leak issue with HTML5 and the iPad.

Scenario:
Publish 30 slide module with practice questions throughout the module and a 10 question quiz at the end.
Minimal interactivity (no custom editing)
Audio on every slide

I publish to LMS with the "Include HTML5 Output" selected.
Published folder size = 60MB
Published to LMS with no issues.

I launch the module on the PC, I have no issues. Everything is working as intended.
I launch the module on the iPad, and the module randomly crashes the browser. The crash happens randomly, but always on a “question” slide. (Either a practice question in the module or on the test at the end) it doesn’t matter.

Articulate states the module is too big, and that a file size of around 10MB is preferable for stability.

I was able to generate a debug txt file from our iPad that recorded my activity from the time I launched the module to the time it crashed.

The log shows that early on in the lesson, this error started popping up in the debug file...

Aug 22 13:55:42  MobileSafari[192] <Warning>: Received memory warning.
Aug 22 13:56:03  MobileSafari[192] <Warning>: Received memory warning.

I had an Apple IT specialist look at it, and he believed that there was a memory leak originating from the code, and that the browser crashed at the moment it ran out of memory.

Unfortunately, the only solution that Articulate has to offer is to create smaller sized modules.

Instructional Designers and Storyline users out there need to be aware of this issue.

Perhaps Articulate will be able to address this memory issue in future updates.

Sad thing is that there is no real alternative at the moment.

4 Replies
steve bogle

I can understand if you are not ready to support the iPad through the mobile safari browser, but please don't advertise that you do.

Tried your support... This is what you sent to our vendor below.

I just want future developers who are looking to use Storyline to produce eLearning through the Safari mobile browser to clearly understand the current limitations.  

We were able to duplicate the issue you reported. Unfortunately, we were unable to determine a workaround.

We have reported this issue to our Quality Assurance team for their review.
I cannot offer a time frame for when or if this issue will be addressed. I would recommend, at this time, to take a different approach so that you continue working on your project.

Regards,

Miker

Customer Support Engineer
Articulate Support - http://www.articulate.com/support/

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