Freezes after importing any size of SQL file

Hello,

for a while when i try to import SQL files using the 'files' => 'execute SQL file' menu, at the end of the process the application window freezes.

I have to close the application from the task manager and restart HeidiSQL.

The import looks good but this behavior is annoying.

Greetings, Sylvain Legrand

And this also happens for small files?

Hi,

I made a test :

1. create a empty base
2. Import a SQL file : 353 Ko => OK

The same process with a 656Ko file => KO

At the end of the process when the popup window closes the application went to the background and you can't reach it.

Greetings, Sylvain Legrand

There were lots of cases in the past where the file was loaded with the wrong encoding. The file open dialog offers the user a drop down with supported encodings. Which one did you select there? If it was ansi, please retest using utf8.

Thank you for your help, but it's still the same behavior.

Previously I left the choice on automatic. Now, I did a test with the choice 'UTF8' => no change = KO

Greetings, Sylvain Legrand.

Is there a chance you send me that file, or does it contain sensitive informations?

Here it is

It's a sql file, change the extension before test it.

Greetings, Sylvain Legrand.

Runs fine here, with the latest build of HeidiSQL.

Only thing to note is that, after the import has finished, when the popup dialog has closed, the main window looses focus, so I have to click once to get back into HeidiSQL. The 108 tables are created and I get no error.

You should really report your environment: Windows/version or Wine/version, and MySQL/MariaDB version.

Hello,

I work on Windows 10 pro 64bit with Wamp server (3.1.9) Apache 2.4.39 + MariaDB 10.3.16 + PHP 7.2.20

You will find the configuration file for MariaDB attached.

For me too, the main window loses focus when the popup dialog is closed, but when I click to return to HeidiSQL, nothing happens!

Greeetings, Sylvain Legrand.

Ok, in that case I suspect that popup window to cause the issue here. I recall there was some other user reporting a similar issue, if it even wasn't the same. Going to search for that. If there's no ticket for that in the bugtracker, then we (say "you" ;)) should create one.

Issue #201 and issue #351 are basically describing the same, while the latter one has less details so I just marked that as a duplicate of issue #201.