Hi friends! I am having trouble figuring out this one. Hopefully you guys can help! My project keeps giving a recursion error message to only Firefox users. I think it has to do with my customization section but im not sure how to fix it while still keeping that part. Do you have any ideas or work-arounds?
I use Firefox and have seen a recursion error on quite a few cogdemo games. It displays Error Too much Recursion or something similar. It seems to be entirely random when it happens since loading a save after reloading the web page fixes it.
Now that you mention it, I seem to recall the back button possibly causing some recursion problems or the like, but I canât find it for the life of me, so I may have dreamt it for all I know.
I did a little testing of your game, which I assume is Last Date Standing judging from your profile picture. I attempted to recreate the error in Firefox, and lo and behold without too much effort, it was actually quite easy to do. I also attempted to do the same thing with a couple of other titles to get an idea of how common the problem is. All of my other tests on the other titles did not yield the same issue. Which would fit the reported pattern of it occurring.
Recreation steps
navigate to the game page in firefox
copy the address
quickly open new browser tabs and paste in the address and enter (1 or 2 was usually enough to trigger the issue)
wait for the dialogue box to pop-up
The only difference I could see from your startup.txt file and the others I tested was that you call a gosub_scene which looks like it runs an image processing function, which will take a lot longer to load than regular text or images. It seems that this delay was meaning the page had not loaded before I opened the next tab and tried to do the same again which somehow made the browser throw a âtoo much recursionâ error.
So my advice at this point should be to use a regular image and remove the gosub_scene from the startup.txt ⌠HoweverâŚ. I doubt this is the only way to force this error, so Iâm not sure how much good it will actually do, and realistically this is a uniquely Firefox issue under some ill-defined yet specific conditions, which is not something you can really âfixâ. User behaviour (opening tabs, reloading pages, clicking too fast) and hardware (processing speed, internet connectivity) can only be mitigated for at the end of the day.
The only thing I can really think of is getting the devs to write some Firefox specific code into the Choicescript JS to handle it somehow. (which is probably beyond the scope of this forum!)