Last modified: 2013-07-25 10:10:17 UTC
Yesterday I uploaded twice many (almost 50) files at once with UW using Firefox 10. In both cases I was warned about an unresponsive script. This happened after I entered description and categories for all files and clicked "next". While the warning about the unresponsive script was shown, this page was still visible. I had to click "Continue" about 5 times before the next page was shown with a list of all files and a spinner to indicate which are currently being uploaded. So there seems to be a loop over all files that takes too long. Using the jquery.async plugin could probably fix this.
I have experienced this bug only yesterday while uploading 5 video files, each about 105 MiB (ca. 530-540 MiB in total). I got it after successfully uploading the files, and filling descriptions for all of them, at the end of the upload process. A browser prompt informed me about an unresponsive JS script, and no matter what I did--I tried waiting for the script to continue, and also killed it and tried going to the next step a few times--I couldn't go further, and had to resign from uploading the files in the end. This occurred while using Firefox 15.0.1 on a 64-bit Windows 7 machine. (I also experience this error while uploading single files bigger than 100 MiB on the same machine, but after a short freeze, the upload process continues just fine. I am not sure if it should be reported as a bug on its own.)
Especially in slow systems Bug 37997 could also slow down the whole thing, while not showing any message of unresponsive scripts.
I'm curious if this is still a problem, as some "big upload" tickets got fixed in the last months.
(In reply to comment #3) Yes, it is. There was someone using Google Chrome (in IRC #wikimedia-commons) on an old machine and they had to click the continue-button in the unresponsive-script-dialog more than 5 times. I didn't ask which machine exactly but my old Pentium IV 1.7GHz is too slow: Uploading more than 15 photos usually leads to this issue. Since it is a JavaScript form and the data entered by the user is not stored in local storage (no resumeable uploads) so everything is lost if the user aborts, I don't think this is of low priority. It happens before the files are being published after clicking the button in the last step. Whatever UpWiz is doing, it should do it step by step using e.g. jquery.async and it should ensure that the user gets a proper message that it will take a while. I've not time to do further investigation.
