I have the same problem for several of the nightly builds. The problem does not occure in the 6.0.0.3603 build. Actually it's problem reoccuring from the pre 6.0 versions.
The dialog of the import progress and the sql both do not update on screen. On the background the import howover does progress. If you wait long enough it will complete.

If have these problems on big databases only. I have one of 350 mb and on of 2GB in both cases the progress is gone.
I use windows 7 even windows detects the program as not responding. It seems there is something wrong with the threads an undating the main thread. Perhaps some of the messages get out of sync between the threads.

The MAX_ALLOW_PACKET size on my database is 32M. So the export creates long insert ignore into..... lines.

But I don't think it's this that causes the problem, eventought thats what i suspected before. It could be however that it contributes. It looks like after finishing the first 5MB the application screen update fails.

I'm also noticing this issue, well always had it, but it's really frusstrating that it hasn't been fixed yet.

I'm running 7.0.0.40.53

"Run SQL file" window doesn't respond, background (main) windows faded, frozen. Not getting any response for like minutes now. I just checked via mysqlworkbench, the data is flowing into the remote database, so it works, but the interface is frozen :(

The imported sql file is 350MB, loaded from file, not into memory.

Oh and how come I can't load the whole file into memory if I do have more than 2GB free? It always says "out of memory" after 1-2 seconds. Is this a bug, or a simple error message because we can't configure the max memory usage?

Don't expect memory usage as high as the size of your file. Indeed memory usage is mostly much higher than the filesize, as there is logic around it, probably some objects holding parts of the file in memory. However, the dialog should get to the end at some point, the fact that the dialog does not respond only tells that it's busy importing the file.