Error: texture released too many times

Randomly our game Nightwalkers.io is freezing with this error:

imageInfo.js:1 Uncaught (in promise) Error: already loaded texture at C3.ImageInfo.LoadStaticTexture (imageInfo.js:1:2448) at animationInfo.js:1:730 at Array.map (<anonymous>) at C3.AnimationInfo.LoadAllTextures (animationInfo.js:1:706) at runtime.js:1:498 at Array.map (<anonymous>) at t.Plugins.Sprite.Type.LoadTextures (runtime.js:1:489) at C3.ObjectClass.LoadTextures (objectClass.js:1:6451) at C3.Layout.MaybeLoadTexturesFor (layout.js:1:12984) at C3.Runtime.CreateInstanceFromData (runtime.js:1:26444)

We started developing more on this 7 year old projects recently and we've been having this error.

I've read some forum posts and supposedly it was fixed 3 years ago. I guess the was resurrected somehow, our never fully fixed.

construct.net/en/forum/construct-3/general-discussion-7/error-already-loaded-texture-143707

construct.net/en/forum/construct-3/general-discussion-7/heck-uncaught-in-promise-174957

construct.net/en/forum/construct-3/general-discussion-7/error-texture-released-times-175126

We don't really have the time to try and isolate this from a 7200 event project projects, so posting it as a bug is out of the question.

We are pulling images from URL (which we saw in other posts talking about this error).

This is the first thing we'll attempt to remove though it will take some time...

Meanwhile does anybody have any more ideas/suggestions we can try?

I'm afraid the reason we have our bug report guidelines is because usually it's impossible to help unless you provide that information. So the best approach is to try to narrow it down to a minimal reproduction and file an issue with that. I'd also caution that if you dig up something from years ago, even with the same error message, I'd say it's best to assume it's irrelevant and your issue is different, especially if it was reported to have been fixed in the end.