Milovana.com

fapnip wrote: Wed May 27, 2020 1:40 pm I've had the same problem. Only option is to manually edit the JSON backup to remove the items, then restore.

AFAIK, no uploaded files are ever truly deleted from EOS. Files appear to be indexed by a unique hash, so if anyone ever uploads the same file again, I think it just de-duplicates, stores a single copy, and records the file's hash in the tease. (Perhaps EOS does some type of garbage collection to find files that are no longer referenced by any tease, but that didn't seem to be the case.)

Thanks fapnip. I haven't had any experience with manually editing the .json file but i'll try and locate where the stuck files are located. Are they usually near the top of the file or somewhere in the depths? Anyway, i'll give it a try. Thanks very much for your help.

So it seems an Eos change has happened overnight and now...things are broken?

I can't load my tease without using private browsing, and it seems anything involving variables and such isn't working so now my tease is unplayable.

Anyone else running into this?


I note that the way instant text is implemented is different now, less flow-y and more jaunt-y, so I assume some update has happened behind the scenes to break things.

Shattered wrote: Sun May 31, 2020 11:23 am So it seems an Eos change has happened overnight and now...things are broken?

Indeed, I rolled out a change ealier today. Can you let me know which tease is not working and how I can trigger the bug?

seraph0x wrote: Sun May 31, 2020 12:58 pm

Shattered wrote: Sun May 31, 2020 11:23 am So it seems an Eos change has happened overnight and now...things are broken?

Indeed, I rolled out a change ealier today. Can you let me know which tease is not working and how I can trigger the bug?

https://milovana.com/webteases/showtease.php?id=40253

It gets stuck on loading modules when I try to go in with my saved profile.

On a private browser, if you e.g. go to code and type 'admin' that's a page number, it won't work.

Or click start and keep playing through the story for a minute and it freezes on any input.

Looks like you can't input some text into variables.
When you go to settings and try to input a custom volume in the settings as a number the tease will freeze.

https://milovana.com/webteases/showtease.php?id=43497

Also the text scrolling looks way more stutter than before.

Any updates on the memory leak bug? Looks like this is the biggest problem at the moment and will still freeze some tease which are using a larger amount of pictures.

viewtopic.php?f=4&t=22630

lolol2 wrote: Sun May 31, 2020 3:44 pm Looks like you can't input some text into variables.
When you go to settings and try to input a custom volume in the settings as a number the tease will freeze.

https://milovana.com/webteases/showtease.php?id=43497

Got it, yeah there was a bug with prompts which should now be fixed. Reload to get the latest client.

lolol2 wrote: Sun May 31, 2020 3:44 pm Any updates on the memory leak bug? Looks like this is the biggest problem at the moment and will still freeze some tease which are using a larger amount of pictures.

viewtopic.php?f=4&t=22630

I have not been able to reproduce this error. I can watch your example tease for hours with no issues. Yes, memory usage does quickly shoot up but it eventually once it pretty much uses all available memory. What I think is going on (at least on my machine) is that Chrome doesn't actually free up memory until its needed for something else. I can only tell Chrome that I don't need a given image cached anymore, I don't control when Chrome actually goes and clears it out of memory.

From the screenshot it looks like you're on Windows, so I'll go and try it on Windows and see if that makes a difference.

lolol2 wrote: Sun May 31, 2020 3:44 pmAlso the text scrolling looks way more stutter than before.

Hmm, not really noticing a difference here. I'll go ahead and also try this one on Windows.

seraph0x wrote: Sun May 31, 2020 4:41 pm From the screenshot it looks like you're on Windows, so I'll go and try it on Windows and see if that makes a difference.

Ok, yeah, on Windows it crashes. Really not sure why it would though - I'm pretty sure I'm freeing up the cached images after I'm done with them. I'll investigate some more.

Thanks, looks like its sorted now!

lolol2 wrote: Sun May 31, 2020 3:44 pmAlso the text scrolling looks way more stutter than before.

Hmm, not really noticing a difference here. I'll go ahead and also try this one on Windows.
[/quote]

There definately is. I'm not sure I mind it, it might even be better, but if it's not intentional thats more of a concern.

Take my tease linked before, it has 5 instant messages in a row - before it would slowly 'slide' past each of them in one seamless motion. Now it prints one. pauses a quarter second, then prints the next.

So, there seems to be a problem going on right now, not sure if it's because of changes being applied to EOS, but right now I cannot load up the tease I've been working on. Wanted to test a few variables and it just gets stuck in Loading Modules.

Also happened with every other EOS tease I try to load normally.

As an example:

Spoiler: show

Edit: Did a few quick checks on a few things. It seems it gets stuck reading the init scripts and can't get past it. So EOS teases without init scripts load up fine, but others get insta-stuck there. Also evals might not be working work right now, but since I can't open up my teases to try them, I can't really confirm this.

seraph0x wrote: Sun May 31, 2020 4:41 pm

seraph0x wrote: Sun May 31, 2020 4:50 pm Ok, yeah, on Windows it crashes. Really not sure why it would though - I'm pretty sure I'm freeing up the cached images after I'm done with them. I'll investigate some more.

Ok, I just pushed an update with a different style preloader and that fixed the issue for me on Windows. @lolol2: Can you test again please?

Shattered wrote: Sun May 31, 2020 4:53 pm Take my tease linked before, it has 5 instant messages in a row - before it would slowly 'slide' past each of them in one seamless motion. Now it prints one. pauses a quarter second, then prints the next.

Gotcha. Part of this update was that I updated dependencies, i.e. I updated the libraries that Eos is using. I'm guessing that the animation library we are using changed how it handles multiple animations in series. I'll check it out.

Thanks for the clear explanation. Most of the time it takes me 80% of the time to reproduce a bug and 20% to fix it, so a good explanation of the expected behavior vs actual behavior with an example tease saves me a ton of time.

Lojackload wrote: Sun May 31, 2020 6:03 pm So, there seems to be a problem going on right now, not sure if it's because of changes being applied to EOS, but right now I cannot load up the tease I've been working on. Wanted to test a few variables and it just gets stuck in Loading Modules.

Edit: Did a few quick checks on a few things. It seems it gets stuck reading the init scripts and can't get past it. So EOS teases without init scripts load up fine, but others get insta-stuck there. Also evals might not be working work right now, but since I can't open up my teases to try them, I can't really confirm this.

Can you give me the ID of a tease that isn't loading? (The ID is the number in the address bar when you are editing the tease in the Eos Editor.)

seraph0x wrote: Sun May 31, 2020 6:36 pm

Lojackload wrote: Sun May 31, 2020 6:03 pm So, there seems to be a problem going on right now, not sure if it's because of changes being applied to EOS, but right now I cannot load up the tease I've been working on. Wanted to test a few variables and it just gets stuck in Loading Modules.

Edit: Did a few quick checks on a few things. It seems it gets stuck reading the init scripts and can't get past it. So EOS teases without init scripts load up fine, but others get insta-stuck there. Also evals might not be working work right now, but since I can't open up my teases to try them, I can't really confirm this.

Can you give me the ID of a tease that isn't loading? (The ID is the number in the address bar when you are editing the tease in the Eos Editor.)

Sent in PM

It seems to load fine in incognito mode, Chrome however it can't load. It seems any Tease with an Init Script isn't loading properly on anything that isn't Firefox or maybe Edge, so it might be a memory leak of sorts?

Lojackload wrote: Sun May 31, 2020 6:39 pm Sent in PM

It seems to load fine in incognito mode, Chrome however it can't load. It seems any Tease with an Init Script isn't loading properly on anything that isn't Firefox or maybe Edge, so it might be a memory leak of sorts?

Works fine for me in Chrome. My best guess is that you have a broken version of the client cached in Chrome. That would explain why it's working in other browsers and in incognito mode. Normally hitting refresh once or twice should clear it.

seraph0x wrote: Sun May 31, 2020 6:50 pm

Lojackload wrote: Sun May 31, 2020 6:39 pm Sent in PM

It seems to load fine in incognito mode, Chrome however it can't load. It seems any Tease with an Init Script isn't loading properly on anything that isn't Firefox or maybe Edge, so it might be a memory leak of sorts?

Works fine for me in Chrome. My best guess is that you have a broken version of the client cached in Chrome. That would explain why it's working in other browsers and in incognito mode. Normally hitting refresh once or twice should clear it.

Well, clearing the cache did do it.

Are there any plans to implement a way to actually delete files that are uploaded to a tease? The current workarounds are kind of a pain.

Lojackload wrote: Sun May 31, 2020 7:49 pm Are there any plans to implement a way to actually delete files that are uploaded to a tease? The current workarounds are kind of a pain.

Yeah, I actually fixed that bug months ago. You ask: What's the reason I haven't released it yet? Well, the Eos editor is using an open-source rich text editor called Slate.js and that project made some massive breaking changes a while ago so when I tried to update that dependency it turned from a five minute update, to a two hour migration, to a ten hour bug hunt, to a 40 hour bang-head-against-wall marathon and it's still buggy as heck after all of that.

Obviously, I could revert back to the old version but that's effort too and it feels like I gotta be getting close now. Maybe I'll take another look at it today but it's taken a lot of patience and whenever I do release the new version there will probably be new bugs in it just because there are so many huge behind-the-scenes changes.