360° Video keeps ressources until leaving the generated html5-output

We observed an effect that in the generated html5-output the resources are not reset after a 360 ° video, but seem to continue to occupy some of the GPU and CPU resources and, depending on the computer, the second or third video no longer plays properly. If we separate the projects - i.e. only one video at one Captivate project - and call them up one after the other, this effect is gone.
Did someone already encountered something similar and found a solution to keep several 360° Videos in ONE Project?
Perhaps this is a more general phenomenon that has little or nothing to do with Captivate. So all helpful hints are welcome ...