Published Issue for Chrome and Microsoft Edge. HELP!

Jul 26, 2021

Hi, few month ago I done a SL project for my client, but today the client requested a little changing (add new VO and content). After revised it, I review in SL and everything work fine. Then I published it and review again, then the issue of "page keep loading", some VO and sound effect unable to play occurred. 

I try to publish the module into a Scene selection instead of whole module, and it work fine.

I try Mozilla browser and it work well and smooth. I try to publish it into Scorm 2004 (ver 4), issue still occured.

Then I found this link and follow the instruction, but no luck.

Edit: my chrome version is Version 92.0.4515.107... i think it auto update a few days ago. So what should I do? Wait for Articulate 360 latest update?


Pls help. (T _T)

Tq and cheer.



10 Replies
Lauren Connelly

Hello Lim!

We are happy to help! It sounds like the audio isn't playing when publishing the course to Review 360 and LMS. Does the audio play when previewing the course in Storyline?

Since this is specific to your project, it would be helpful to test your project on my end. You can attach the .story file to this public discussion or upload it privately in a support case.

Lim CH


tq for your replied.

Some of the VO stop and unable to play,  when I drag the timeline or press previous button. After many attempted, I just upload to TalentLMS according to the method from the link

It work in both Chrome and Edge browser. But I download the zip file and unzip it, review in local computer, it crash. I send the Zip file to my friend, he/ she also having the same issue.

Edit: I try with other latest modules, issue still occurred. I noticed the issue occurred when it come to Quiz/ Exercise section like drag and Drop. If i drag the timeline under the quiz slide, and click submit button, the sound effect of the layer (correct or incorrect) cannot be play. Then i click previous button to go back to the previous page, the VO cannot be play in the previous slide.

I click Next button back to the quiz slide, the VO unable to play from the beginning of the slide... click Next and Next.. and VO also cannot be play for the rest of the slide. Animation all working good except the VO. If i keep pressing Prev, Next and refresh button, the slide crash.

Now all the review progress is done with Mozilla browser. Hope next update will solve this problem.


Dan Parker

I posted this in another related post, but to raise awareness, I am also posting here since it seems to be the same issue as this. We are also experiencing this issue with many of our courses. This is causing many of our video and audio assets within longer courses to fail to load and playback. This is obviously a MAJOR issue. @Articulate, are you looking into an update to address this? While the problem is Chromium putting a limit on WebMediaPlayer instances, we cannot wait until they either revert or increase this limit.

It looks like either the loading of media files needs addressed, or older/unused instances of WebMediaPlayer need to be correctly removed; there is no reason that more than 75 WebMediaPlayer instances should be reached just by loading the 1st slide of a course which only has 1 video per slide. My only guess is that perhaps Storyline is creating WebMediaPlayer instances for ALL media files upon course load; if so, is there anyway to change or suppress this from happening?

Dan Parker

UPDATE: (I also posted this in the other thread.)  In doing a bunch of testing, I have confirmed that SL360 creates separate WebMediaPlayer instances equal to the number of video files that exists in a published course upon startup. Therefore, since the current limit for WebMediaPlayer is 75 for desktop and 40 for mobile within Chromium right now, ANY course with more than 75 (or 40 if mobile is a concern) videos will break and exhibit this error.

Dan Parker

Thanks Leslie! You are correct, while Google is increasing the limit of the WebMediaPlayer in an update next week, however, this will most likely not be the long term solution.

The WebMediaPlayer limit is being raised to 1000 only until Chromium determines the final limit and communicates it out. I suggest that Articulate might want to be proactive in finding out a solution, or workaround, to cut down on the number of concurrent WebMediaPlayer instances before Chromium cuts the limit down again. Otherwise, some of us will be left with broken or unplayable media again in a few months time and will be scrambling to find a solution.

Leslie McKerchie

Hi Lyn,

I apologize. It looks like we missed your reply here. I have not seen similar reports tied to publishing, but we'd be happy to help you.

I'm curious if the issue happens in any course you are working on or just this particular one? Are you able to preview this course?

  • If you cannot re-create the issue in a new course, I recommend importing the file into a new one and proceeding.
  • If it's happening in any/all files, you should conduct a repair of your software.