Encountered the strangest glitch in nyx - brought up an image I've never seen before.
- Shattered
- Experimentor
- Posts: 1238
- Joined: Fri Jan 11, 2013 6:41 pm
- I am a: Switch
- Location: United Kingdom
Encountered the strangest glitch in nyx - brought up an image I've never seen before.
I uploaded a file to the nyx editor, it looks fine. When I go to add it to my web tease, another image comes up. I've never seen it before, it's not from my PC. I can only assume Nyx somehow pulled it from somewhere else on the system, and that kinda seems like it could be really bad for the backend. I renamed it and uploaded it so not a problem for me personally but I feel it should be noted.
Salutations, Stranger.
--
Like my work and want to see more? Consider supporting my Patreon or buying me a Ko-fi!
Try my teases on Milovana!
--
Like my work and want to see more? Consider supporting my Patreon or buying me a Ko-fi!
Try my teases on Milovana!
-
- Explorer
- Posts: 26
- Joined: Thu Feb 16, 2017 5:13 am
- Gender: Male
- Sexual Orientation: Straight
- I am a: Switch
Re: Encountered the strangest glitch in nyx - brought up an image I've never seen before.
been happening to a lot of us. sadly.
Re: Encountered the strangest glitch in nyx - brought up an image I've never seen before.
Hmm, I'm not sure what would cause that.
Re: Encountered the strangest glitch in nyx - brought up an image I've never seen before.
Hey,
I am currently converting my Maze of Passion 2 tease to Nyx. I noticed that nyx displays on several pages a wrong picture. It's always the same picture showing a 3D-character. I haven't uploaded it and in the media section the correct picture is shown...
The wrong picture which is shown on several pages The picture which should be displayed in this example I'll try what Shattered did, but it's kinda annoying to check 1500+ pages
The tease id is 35105
I am currently converting my Maze of Passion 2 tease to Nyx. I noticed that nyx displays on several pages a wrong picture. It's always the same picture showing a 3D-character. I haven't uploaded it and in the media section the correct picture is shown...
The wrong picture which is shown on several pages The picture which should be displayed in this example I'll try what Shattered did, but it's kinda annoying to check 1500+ pages
The tease id is 35105
Cock Hero - Overwatch 3 is out! viewtopic.php?f=25&t=22817
Re: Encountered the strangest glitch in nyx - brought up an image I've never seen before.
This is a fascinating bug - I'll try to shed some light on the situation, although I don't totally understand it myself yet.
First, some background. Milovana uses a virtualized file system. When you upload a file, it is hashed, the name is stored in the database with a pointer to the hash of the image. The image itself is then stored under that hash. That way, when multiple people upload the same image we only have to store it once.
Those of you affected by the glitch are all seeing the same picture. It is the second-oldest picture in the virtualized file system, ID=2.
The bug occurred exactly 380 times since 2012 when it first occurred. In that time roughly 247000 images have been uploaded, so the bug affected approximately 0.15% of uploads. But when it struck it often struck several times in a row.
Another peculiarity is that the images pointing to the wrong image are all marked as size=0 in the virtual file system. In other words, something must be going wrong during the upload that corrupts the upload process and it tends to happen several times over a short period and then not at all for potentially a very long time.
@Venus: I pulled the list of affected images from your tease:
I'd like to fix the issue permanently of course, but right now I'm not sure where to even start. Is there anything you guys can think of that might have triggered the bug?
First, some background. Milovana uses a virtualized file system. When you upload a file, it is hashed, the name is stored in the database with a pointer to the hash of the image. The image itself is then stored under that hash. That way, when multiple people upload the same image we only have to store it once.
Those of you affected by the glitch are all seeing the same picture. It is the second-oldest picture in the virtualized file system, ID=2.
The bug occurred exactly 380 times since 2012 when it first occurred. In that time roughly 247000 images have been uploaded, so the bug affected approximately 0.15% of uploads. But when it struck it often struck several times in a row.
Another peculiarity is that the images pointing to the wrong image are all marked as size=0 in the virtual file system. In other words, something must be going wrong during the upload that corrupts the upload process and it tends to happen several times over a short period and then not at all for potentially a very long time.
@Venus: I pulled the list of affected images from your tease:
- Spoiler: show
I'd like to fix the issue permanently of course, but right now I'm not sure where to even start. Is there anything you guys can think of that might have triggered the bug?
Re: Encountered the strangest glitch in nyx - brought up an image I've never seen before.
Thanks for the list, that helps a lot.
Just a glance at the list and I noticed every single picture is actually part of the pictures I had to scale down, because they were too big at first to upload. The file size (~2.8 MB) is not the only limit for upload, the resolution is too. When trying to upload a picture which resolution was to big I got two weird error-boxes. One error message I can recall, because I searched for it in the forum: [IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error #2038"]
But I guess that error message is thrown for many different reasons.
Not all of the scaled down pictures are affected. The reason could be that once I got the error I at first tried to upload picture wise: try upload -> got error -> resize -> upload again.
I did this for the Ariel set and very many of these pictures are affected.
Once I realized if one picture of the set is affected the others are most likely also (at least at high risk), I started to resize the whole set when I got the error. That's the case for the meganrain and india sets. Only the first picture is affected.
As I noticed the resolution is a thing I resized a few sets before trying to upload and those aren't affected at all.
I conclude when uploading a picture which resolution is too big and the error message pops up the corrupted entry must be generated.
Just a glance at the list and I noticed every single picture is actually part of the pictures I had to scale down, because they were too big at first to upload. The file size (~2.8 MB) is not the only limit for upload, the resolution is too. When trying to upload a picture which resolution was to big I got two weird error-boxes. One error message I can recall, because I searched for it in the forum: [IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error #2038"]
But I guess that error message is thrown for many different reasons.
Not all of the scaled down pictures are affected. The reason could be that once I got the error I at first tried to upload picture wise: try upload -> got error -> resize -> upload again.
I did this for the Ariel set and very many of these pictures are affected.
Once I realized if one picture of the set is affected the others are most likely also (at least at high risk), I started to resize the whole set when I got the error. That's the case for the meganrain and india sets. Only the first picture is affected.
As I noticed the resolution is a thing I resized a few sets before trying to upload and those aren't affected at all.
I conclude when uploading a picture which resolution is too big and the error message pops up the corrupted entry must be generated.
Cock Hero - Overwatch 3 is out! viewtopic.php?f=25&t=22817
-
- Explorer
- Posts: 5
- Joined: Mon Jul 18, 2016 10:46 pm
- Gender: Male
- Sexual Orientation: Straight
- I am a: Submissive
Re: Encountered the strangest glitch in nyx - brought up an image I've never seen before.
I'm getting this error pretty frequently as well. What exactly is the resolution threshold to avoid this error?
Who is online
Users browsing this forum: No registered users and 1 guest