EOS limits?

[Orion_be]

I'm planning an estim adventure tease, but first I like to know if there are any restrictions in size of a tease?
My first idea involves 36 rooms with about 20 pages each. To keep things interesting I want to have several picture options so each room needs about 75 pictures. This makes over 2500 pictures. Can I upload that amount of pictures to my EOS tease? I will separate them into multiple folders of course.

[seraph0x]

There aren't any hard limits. I'd be curious to hear if anyone has been running into performance issues while making large teases and what they were. If there are issues, that's definitely something that could be further optimized though.

[Roblsforbobls]

There aren't any hard limits. I'd be curious to hear if anyone has been running into performance issues while making large teases and what they were. If there are issues, that's definitely something that could be further optimized though.

Here's something I saw on the forum a little while ago. Not sure if it's related, relevant, or even a bug, but this is what I thought of when I read Orion_be's post: viewtopic.php?f=6&p=275674#p275674

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

[Faraday]

There aren't any hard limits. I'd be curious to hear if anyone has been running into performance issues while making large teases and what they were. If there are issues, that's definitely something that could be further optimized though.

There's also a tease storage limit for the data that persists between visits to the tease (I think you may need to have an account and be logged in to get these features). Based on the linked thread, it actually seems an incredibly small limit (so much so that people are considering ways to workaround it).