Frequent CRASHES running long queries or loading SQL files with no default THEME

[robman70]

Steps to reproduce this issue

1. Run a long query (maybe only loading SQL files but I'm not sure about this);

Current behavior

Frequent crashes occur using a non default theme (e.g. Windows 10 Dark)

Expected behavior

No crashes... :-)

Possible solution

Environment

• HeidiSQL version:
  HeidiSQL 10.1
• Database system and version:
  MariaDB 10.1
• Operating system:
  Windows 10 Pro

[DizzyC]

I can confirm this issue.
And it happens with the Material Theme that is now selectable from the install screen.

Happens every time I 'Run SQL script'. Consistently reproduces with bigger scripts. A script over ~150MB will crash every time.
I don't get the crash popup dialog, it seems the gui just breaks down.
First indicator is the progress bar that disappears and is replaced by a weird pulsating dark shadow :)

But the process continues, the SQL script is executed to the end.
After it finishes and the progress dialog disappears the whole interface breaks down (various surfaces become blank white).
The app seems to partially continue to work, I can select dbs, tables etc. but It's not really usable and I can't close the app anymore. Need to kill it and restart.

[robman70]

At the beginning I also thought the same thing but then some scripts crashed even using the default theme ... :-(

[jjasoncool]

I have the same problem, this will happen after executing the mysql dump file.
And the delete button sometimes fails, you can only use the backspace key to delete the string in the editor (it is normal in video).
Video_2019-07-05_165640.zip

[aruldd]

Experiencing the same issue with the same theme. It crashes consistently.

[WesleyM77]

Can confirm this issue. I've experienced it multiple times with the Material theme.

[ansgarbecker]

I found the myriad of refreshes after each query can confuse the application, so my just pushed change reduces that from one call per SQL command down to one call per second. It helps at least here, in case of one bigger file with many short queries.
Please update to the latest build and report back if that already helped.

[DizzyC]

@ansgarbecker I'm sorry to report the last build has not fixed the problem. (running 10.2.0.5684 (64 Bit))

I'm having the exact same issues. Noticed that at about 1 mil, 1.2 mil imported rows the UI breaks.
(I encounter this issue when importing bigger dumps, 200MB plus, dumps generated also by heidisql)

Thanks for the effort!

[WesleyM77]

Still an issue. Seems to break the UI before it actually finishes running the file.

[ansgarbecker]

Please update to v10.3 and report back if this is fixed. In #654 there is comment saying this is fixed, but it may have a different cause.

[DizzyC]

Sadly no change for me :(

Tested on version 10.3 and the behavior was exactly the same for me, no change, no improvement.

Let me know if I can assist further.

[WesleyM77]

Still seems to be an issue even after I've done what the comment on #499 mentioned.

[michalwoz]

this bug is still present in 11.0.0.5937 while running ~80MB .sql files

[ansgarbecker]

I just pushed various updates for this progress dialog. Only a single instance of that progress dialog is used for multiple files. Also, there are no more refreshes in the background. For more technical details, see #338

Also related: the progress dialog no longer uses the user selected theme, which makes it more stable I hope. See 43a114c

My tests with 20mb SQL files were without errors, but someone should check the dialog with some larger file.

[michalwoz]

80MB import:
Previously it didn't crash only once per ~20 attempts.
Now 5/5 success!
So it seems to be fixed.

[WesleyM77]

Tested twice with a ~350Mb import. Didn't crash on either. Agree that it appears to be fixed!

[ansgarbecker]

Cool!

[lefin17]

I have same problem, but in my case when try to send big query from different clients the problem is the same. When query is short (ex. less then 1000 symbols) every is ok, but when I have long query (for me more then 2k symbols) the system (application) is not recieve any answer from remote sql server. But not from any workplace. From linux station is ok, from notebook with w11 - is ok, but remote terminal servers (WS2019) and WS2013 - has problem with long queries... and some of them via VPN, some in same network...