Welcome to the in5 Answer Exchange! This a place to get answers about in5 (InDesign to HTML5) and make requests.
0 votes
I am using in5 for very large high definition single page progressive web apps (250 megabytes). I have began getting the below errors in Google Chrome. These errors were always present in alternative Chromium browsers like Kiwi, but in the newest version of my exports they seem to have increased in severity and now occur within Chrome as well. It appears that it may be a recursive loop problem based on the wildcard used in the "initClickEvents" function... Not sure if it is a bug, or something in my html... Any ideas? I can upload it and send a link to a site, but I would want to send it via email since the client is unlikely to want it published openly.

Below is the Chrome Dev Tools error details:

jquery.min.js:2 jQuery.Deferred exception: Maximum call stack size exceeded RangeError: Maximum call stack size exceeded

    at se.select (https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js:2:22934)

    at Function.se [as find] (https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js:2:7089)

    at S.fn.init.find (https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js:2:25014)

    at initClickEvents (file:///C:/Users/mark/Documents/Local%20Indesign/CIOB%20FH/App/Arranger/assets/js/in5.config.js:561:35)

    at HTMLDocument.<anonymous> (file:///C:/Users/mark/Documents/Local%20Indesign/CIOB%20FH/App/Arranger/assets/js/in5.config.js:960:3)

    at e (https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js:2:30005)

    at t (https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js:2:30307) undefined

S.Deferred.exceptionHook @ jquery.min.js:2

jquery.min.js:2 Uncaught RangeError: Maximum call stack size exceeded

    at se.select (jquery.min.js:2)

    at Function.se [as find] (jquery.min.js:2)

    at S.fn.init.find (jquery.min.js:2)

    at initClickEvents (in5.config.js:561)

    at HTMLDocument.<anonymous> (in5.config.js:960)

    at e (jquery.min.js:2)

    at t (jquery.min.js:2)
in misc by (440 points)

1 Answer

0 votes
by (18.3k points)
That was my original thought as well, but the version that is currently working in Chrome is actually larger than the newer version... I will upload it and email over a link through the contact page. Thanks!
I'll keep an eye out for your email. Thanks :)
I think that the multistate object video popups and some of my custom code are causing a loop. I was able to get the export to work without errors when all of my custom code was removed. Most likely it is the javascript code that tells the lightbox to open in full screen. I am doing some process of elimination export tests to pinpoint the exact conflict.
This javascript function seems to be the cause of the loop problem. Any ideas on modification of this code or an alternate css / html approach to full size iframes?


if($.colorbox) {

        $('.lightbox').filter(':not([href*=lightbox\\=0])').colorbox({iframe:true, width:"100%", height:"100%"});

        $('svg .lightbox').on(clickEv, function(){

            $.colorbox({iframe:true, width:"100%", height:"100%", href:$(this).attr('xlink:href')});

            return false;


        $('.thumb').colorbox({maxWidth:"95%", maxHeight:"95%"});


I'll check with our developer.
Unfortunately, the colorbox code snippet has proven to be a red herring… I have had error free exports adding it back in as well, and removing it from errored exports does not fix the problem.

I also had errors on an export this morning without the mso video pop up, that was error free last night with only minimum changes. Back to square one…
Thank you for the update. To clarify, are these the same errors that you were seeing in the Console, or are they errors that you're getting during your in5 export?

We previously received your links via email. We would be happy to take a look at your InDesign file or a sample file that recreates the issue to further troubleshoot.
I will attempt to reduce my file size to something more conducive to packaging, and retain the call stack errors. I doubt it would be possible to package / use the full sized file. I am still struggling with the inconsistency of the call stack errors at this point, so it may take a while to get a smaller version that regularly recreates the issue.

A smaller version would be great. If it helps, you can send files up to 2GB via Wetransfer.