It looks like there is a heavy memory bug in the EOS player... I just wondered why
my tease stopped working after an hour and then saw that firefox is using 5,9GB memory.
I just tried to reproduce this with a very simple script.
Showing a random picture and then jumping back to the page.
https://milovana.com/webteases/showteas ... e8a76525d1
This issue seems a lot stronger with firefox, takes only 2-3min to claim 5gb+ memory.
Chrome is a bit slower but still 3gb+.
Only MS Edge seems to work a bit better but also claims more and more memory over time.
Of course this example has a crazy amount of picture changes but something seems to make it even worse in my tease.
Maybe the little code or audio functions I don't know.
The 5,9gb were only after ~150 random pictures + ~20 fixed pictures and ~15 different audio files.
Other users has also reported to have random problems with my tease, stopped audio, no picture change, notification buttons missing etc... I guess that could be the memory problem.
Even with 32gb memory the tease stopped working with 6gb in use at firefox.
You can try it with my tease too, just go to the settings and set the min time to 1s and max time to 2s, then skip the intro and let it run for 10min, should also claim over 3gb in firefox.
Anyone can reproduce this problem too?
Even if I did something wrong in my script this should not happen right? :)
But of course every comment about fixing this in my script is welcome.
Edit:
Okay found the thing that makes it even worse.
When you have a page that jump to a random page that shows a random picture from a galerie, it will go crazy.
Crashes the tease within seconds.
Test2:
https://milovana.com/webteases/showteas ... c4a9b88b22

- 2020-01-06 23_36_19-Eos Editor.png (70.27 KiB) Viewed 3692 times