Thanks for confirming, Sinchu. Like Leslie mentioned, that is a lot of media for mobile devices to handle. The responsiveness of the content in mobile browsers will generally be slower than desktop browsers. The device version that you're using can also impact mobile browsers' performance. New models have more memory, which means your HTML5 content may be slower to respond in older models.
Is the performance issue related to the time it takes to load the content? Are you seeing crashing of the content?
Thanks for that detail, Sinchu. We are looking into how some courses are crashing on mobile devices. I'm going to connect this discussion to our report.
To help us test, if you'd like to share that .story file with us, you can upload it here. Also, let me know if you're using any special fonts. They can impact the overall memory needed to load the output, so that's a good clue. Thanks again!
I have done detailed debugging and deleted some of the videos and audios then i could see the performance is much better.
Can you please confirm Is storyline is using any player to launch the videos/audios? i think the media player is causing the issue, the way auto play function is programmed for audio is crashing sometimes and its slow down the performance.
Try this and you will be able to find the issue in desktop browser also.
Create a storyline file with 5 pages and include a lengthy audio(1 Hour Audio) in slide 3 and publish it for SCORM cloud and try to test the build.
Reproduce the “out of memory” crash:
1. Close all Chrome instances (validate this has happened with task manager). 2. Launch the training course 3. Quickly click “Next” twice to advance from the second to the third slide. 4. Chrome will then try to allocate more than 2GB of RAM inside that single process and crash. Please see the attached image for reference.
7 Replies
Hey Sinchu,
Sorry to hear that you've run into difficulty with your project.
What version of Storyline are you using and how are you publishing/sharing the content?
That does sound like some pretty heavy content loading though.
I have used storyline 360 and tested using scorm cloud
Thanks for confirming, Sinchu. Like Leslie mentioned, that is a lot of media for mobile devices to handle. The responsiveness of the content in mobile browsers will generally be slower than desktop browsers. The device version that you're using can also impact mobile browsers' performance. New models have more memory, which means your HTML5 content may be slower to respond in older models.
Is the performance issue related to the time it takes to load the content? Are you seeing crashing of the content?
Yes sometimes the course is crashing and some times audios and videos are not loading .
When i revisit the course without clearing the browser cache the course is loading fine so the issues is with loading only.
Thanks for that detail, Sinchu. We are looking into how some courses are crashing on mobile devices. I'm going to connect this discussion to our report.
To help us test, if you'd like to share that .story file with us, you can upload it here. Also, let me know if you're using any special fonts. They can impact the overall memory needed to load the output, so that's a good clue. Thanks again!
Hi Cystal,
Yes we have used the CAlibri fonts,
I have done detailed debugging and deleted some of the videos and audios then i could see the performance is much better.
Can you please confirm Is storyline is using any player to launch the videos/audios? i think the media player is causing the issue, the way auto play function is programmed for audio is crashing sometimes and its slow down the performance.
Try this and you will be able to find the issue in desktop browser also.
Create a storyline file with 5 pages and include a lengthy audio(1 Hour Audio) in slide 3 and publish it for SCORM cloud and try to test the build.
Reproduce the “out of memory” crash:
1. Close all Chrome instances (validate this has happened with task manager).
2. Launch the training course
3. Quickly click “Next” twice to advance from the second to the third slide.
4. Chrome will then try to allocate more than 2GB of RAM inside that single process and crash. Please see the attached image for reference.
Hi Sinchu,
I see where you reached out to our support team to discuss an issue and share some ideas about the same time you filed this latest response.
I've added the details shared here in the comments of your support case for Miker.
This discussion is closed. You can start a new discussion or contact Articulate Support.