Captivate 2019 and Chrome freeze, not loading a project

[#1]

Hi, I'm having this issue with Captivate and Chrome 73.0.3683.86 (Official Build) (64-bit).

The course will freeze on loading (published in SCORM):

or load an empty background and stop (reporting disabled):

At the same time it works in IE, Firefox, and when uploaded online it also starts working in Chrome too. It only affects launching in Chrome locally. Has anyone encountered anything like this?

[#2]

Hi, I'm having this issue with Captivate and Chrome 73.0.3683.86 (Official Build) (64-bit).

The course will freeze on loading (published in SCORM):

or load an empty background and stop (reporting disabled):

At the same time it works in IE, Firefox, and when uploaded online it also starts working in Chrome too. It only affects launching in Chrome locally. Has anyone encountered anything like this?

[#3]

If the same output works when uploaded to an LMS or web server then the issue is just due to restrictions placed on the content by your browser when played locally.  This can happen due to security settings in the browsers because stricter security measures are always being implemented by browser manufacturers.

I have seen issues where Chrome believes the SCORM content is trying to launch a popup window and the security settings in the browser prevent this, so everything grinds to a halt.  If you work in an organisation where the IT department prevents you from relaxing the browser security then you would be pretty much unable to use Chrome in this situation.

[#4]

Thanks for your reply! Agreed it's something local and I narrowed it down to Chrome only. The same content works in IE and Firefox, but gets stuck while loading in Chrome or the background graphics displays and freezes. It happens both with SCORM and reporting disabled, regardless of any publish settings combination. I applied all the past fixes for deprecated functions in JS that caused problems with Chrome a few years ago, but nothing seems to help. It's pretty frustrating for local testing and when sending someone a package for a quick review when most people use Chrome these days. Interestingly, the same courses used to work in Chrome locally, so my guess is there was some browser update meanwhile. Do your courses work in the newest Chrome locally?

[#5]

Yes they do.  I am using Chrome version 73.  But I am only publishing to HTML5.  Are you?

[#6]

Yep, same here. HTML5 only.

I'm trying to narrow it down further and was launching random, older courses in Chrome. And interestingly some of them work, but only published in any SCORM. With reporting disabled, they are stuck on a forever-loading screen too. Now I'm hunting for any exclusive objects/code in the courses that won't launch, but they are in the same template and so far they look identical. I would blame it on some random corruption, but when I upload them to the LMS, they work again.

Here's what Chrome console says when launching an HTML5 course with reporting disabled. There are no .png files in the /dr folder, but that's the case for the courses that work too.

[#7]

Those errors are usually associated with JSON not being enabled on your web server.

[#8]

I have very similar problems - my SCORMs html5 courses, generated from CP 2019.0.1 and placed at Moodle, loads in Chrome randomly correct or freezes ,,forever". So after I close popup window and relauch course, then it loaded quick an correctly. It happens on my desktop, tablet or mobile devices.

I tried to republish, resign-in, restart... No success. This is frustrated situation, because mymy commerci clients asks me, what they can do. For any help, thank you.