Description of problem: When uploading a large batch of files, the explore.exe stopped working. The website froze, and stayed frozen. I was unable to upload my observations.
Step 1: Upload a bunch of photos
Step 2: ???
I’m not really sure what caused this. I don’t know if I will be able to replicate this.
My internet should be pretty fast, but I did notice some of the elements of inaturalist were slow. Perhaps its something to do with lots of people uploading to inat due to the city nature challenge.
This just happened to me again, and these are the logs, however, I’m not really sure what to think about the location error. It’s able to find a location for all of the pictures.
the same issue happens to me sporadically using Opera (back when I used to use Chrome, it never happened once). I haven’t managed to figure out yet exactly what triggers it, but it’s some kind of sequence of clicks/keystrokes, and then the screen enters this frozen state where you can’t do anything except for pick up images with your mouse. Either just slightly moving one, or dropping one image onto another to merge the two, will fix the error.
It’s happened to me when uploading small images, large images, just 1-3 images at once, up to 100 images at once; there doesn’t seem to be consistent conditions under which the error only occurs (for me at least)
This freeze happens before you hit “Submit”, correct?
Unfortunately I think your screenshot is a bit too small to read clearly. Do you have a full-sized version somewhere you can email to help@inaturalist.org?
I’m going unmark this as “solved” because the underlying issue hasn’t been solved yet. Ideally this wouldn’t happen at all and you wouldn’t need the workaround @thebeachcomber proposed.
Just a heads-up that all large images are resized on iNat so that their long edge is no more than 2048 pixels. You might try exporting them so that they’re no more than 2048 pixels on the long edge. That’s what I do for my 45 mp camera images. Could make the whole process go a bit more smoothly, although as thebeachcomber said, it may not solve this issue.
