Loading Profile...
It doesn't work - keep getting an "unexpected error".
In my first try (a 8000x16000 png) it always fails during the "Converting..." phase with a "Sorry, an unexpected error occurred" message.
http://seadragon.com/view/1e2
http://seadragon.com/view/1e2
I’m Unhappy
3
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
The best solution from the company
-
We've got great news -- we've fixed these common out-of-memory errors! We went ahead and retried the image, and it worked now!
http://seadragon.com/view/1e2
Let us know if you encounter an "unexpected error" again.
I’m happy
The company says
this solves the problem
-
Inappropriate?I checked out the log for 1e2 now, and it looks like we're running out of memory right at the end of our conversion. But the worst part is that it does so right at the end (94%). We'll look into this more and get back to you. Thanks for bearing with us!1 Comment Add a comment
This solves the problem
-
Hm, I didn't mean to mark this as "solves the problem", not sure why it's doing that. The problem isn't solved yet. ;) -
Inappropriate?Aseem, after two successes (http://seadragon.com/view/yx, http://seadragon.com/view/160), I, too, experienced the same thing this morning with this November version of Blue Marble (http://seadragon.com/view/13m).
I was curious as to whether the Seadragon link would remain the same for a given image even if it were input to the site multiple times/by multiple people and of course you guys have done the intelligent thing by not allowing duplicate DZIs for the same URL. I'm wondering what this means for bugfixes.
When you repair whatever is causing the conversion to fail, will your server automatically try to rebuild all images that have previously failed? Presently, if anyone else on the net tried to put in that exact Blue Marble image, they would instantly hit the failure message with the Retry link. I fear that you'll lose a significant number of users due to them not being willing to click 'Retry'.
Wouldn't it be safer to assume that if an image has failed before and someone (anyone) enters that URL again that they would naturally hope to retry the conversion if it has previously failed? It seems like the converter should recognise the failed conversion state of an image and immediately retry conversion when the URL is entered a second (or more) time.
I realise that you guys probably want to keep your Azure servers from constantly grinding on repeat requests and I assume that there are hostile people out there who will attack the service by constantly submitting a URL known to fail after a long period of computation. Unfortunately at the moment there doesn't seem to be a difference between a broken URL and a valid URL whose conversion didn't go well as far as Azure knows.
Anyway... I'm just curious about what your thoughts are as far as the second and third user's experience when they input an image URL that someone else has already tried and experienced failure with.
All the best to you guys!
I’m thankful
1 Comment Add a comment
This solves the problem
-
I think retrying automatically when someone re-submits an URL is a decent and interesting idea. We talked about actually checking if the source image had changed as well, but that was too much for v1. But just retrying in the case of an error is easy to do.
The only downside is e.g. if it's a large image and we're running out of memory after 20 minutes, it sort of sucks to make someone wait 20 minutes again. But most of our other error cases all happen pretty fast (e.g. the source image doesn't exist), so I think overall this is a good idea. Thanks! -
Inappropriate?13m (the Blue Marble photo you posted) actually didn't run out of memory; we had an obscure timeout error on the Azure storage side. I've restarted it and hopefully it works this time.
Btw, over time we'll keep making specific error messages (e.g. "we ran out of memory"), but for now, if you run into an internal error, just post it here and I'll take a look and let you know what the issue is.3 Comments Add a comment
This solves the problem
-
Understood. :)
-
There you go, 13m worked this time. Btw, it shows only South America and not the entire Earth -- is that a mistake? I can't view the original, my browser says it has errors.
-
Yeah, sorry about that. I was surprised as well... I suppose I should have read the PDF here: http://visibleearth.nasa.gov/view_det...
I was looking for a png version of the whole globe for November and looked under details. I found what appeared (according to the resolutions) to be what I wanted, but failed to read the documentation.
(Where have I heard of that being a common affliction recently?... Haha. Whoops.)
Anyway, thanks for the help. -
Inappropriate?On the theme of other errors, I was having a 304 error thrown repeatedly last night when I was attempting to show my father how easy it would be for him to use this (he works at his home from his iMac) using images he has hosted on Windows Live Photos. I made sure that the photo in question was publicly accessible and threw the address to seadragon.com, but it just didn't want to take it. I will admit that the URL was horrendously long and the filename had spaces in it, so I'm not sure if those were the cause or not. I've since deleted the file as an example but will try to duplicate the error for your analysis.3 Comments Add a comment
This solves the problem
-
Right, here it is as promised: http://seadragon.com/view/2mn
"We got a 304 NotModified error at the URL you gave us."
Interestingly when the filename was changed to a single word, it worked just fine. See: http://seadragon.com/view/2me -
Very strange. We saw this for the first time on the day we shipped, also when the source photo was on Live. The fact that it works when the filename has no spaces is very interesting -- I bet that'll help us narrow down the cause eventually.
Sorry for the trouble -- hopefully you weren't too embarrassed when it wasn't "just working" =P -- but thanks for your repro! -
We fixed this "304 NotModified" error related to Live SkyDrive also. I retried your original image, and it works now too: http://seadragon.com/view/2mn =)
-
Inappropriate?We've got great news -- we've fixed these common out-of-memory errors! We went ahead and retried the image, and it worked now!
http://seadragon.com/view/1e2
Let us know if you encounter an "unexpected error" again.
I’m happy
The company says
this solves the problem
EMPLOYEE
