Heidi crashes on Windows 10 x64 build 17134 - Access violation

jbeitler posted 3 months ago in General

Please assist. I think Heidi has a lot to offer but can't use it because it constantly crashes.

This is a new install.

date/time : 2018-06-18, 14:35:11, 37ms

computer name :

user name :

registered owner : temp / Microsoft

operating system : Windows 10 x64 build 17134

system language : English

system up time : 3 days

program up time : 16 seconds

processors : 4x Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz

physical memory : 1707/8049 MB (free/total)

free disk space : (C:) 197.44 GB

display mode : 2560x1600, 32 bit

process id : $77cc

allocated memory : 92.42 MB

largest free block : 131025.96 GB

executable : heidisql.exe

exec. date/time : 2018-06-18 14:18

version :

compiled with : Delphi XE5

madExcept version : 4.0.12

callstack crc : $b97fef7e, $39af944f, $39af944f

exception number : 1

exception class : EAccessViolation

exception message : Access violation at address 0000000000865097 in module 'heidisql.exe'. Write of address 0000000000000058.

main thread ($9334): 00865097 heidisql.exe SynTextDrawer 924 +7 InitETODist 008652d7 heidisql.exe SynTextDrawer 974 +1 TSynTextDrawer.ExtTextOut 0088c29a heidisql.exe SynEdit 3975 +66 PaintToken 0088cca2 heidisql.exe SynEdit 4131 +63 PaintHighlightToken 0088f4fd heidisql.exe SynEdit 4624 +215 PaintLines 0088f8ed heidisql.exe SynEdit 4694 +53 TCustomSynEdit.PaintTextLines 00887b4c heidisql.exe SynEdit 2906 +61 TCustomSynEdit.Paint 006a6856 heidisql.exe Vcl.Controls TCustomControl.PaintWindow 0069d603 heidisql.exe Vcl.Controls TWinControl.PaintHandler 006a408d heidisql.exe Vcl.Controls TWinControl.WMPrintClient 0040d90e heidisql.exe System TObject.Dispatch 00695ca3 heidisql.exe Vcl.Controls TControl.WndProc 0069d36e heidisql.exe Vcl.Controls TWinControl.WndProc 0089c5a6 heidisql.exe SynEdit 8581 +22 TCustomSynEdit.WndProc 00695780 heidisql.exe Vcl.Controls TControl.Perform 0069e553 heidisql.exe Vcl.Controls TWinControl.WMPaint 006a67e8 heidisql.exe Vcl.Controls TCustomControl.WMPaint 008988a8 heidisql.exe SynEdit 7370 +16 TCustomSynEdit.WMPaint 0040d90e heidisql.exe System TObject.Dispatch 00695ca3 heidisql.exe Vcl.Controls TControl.WndProc 0069d36e heidisql.exe Vcl.Controls TWinControl.WndProc 0089c5a6 heidisql.exe SynEdit 8581 +22 TCustomSynEdit.WndProc 0069c5aa heidisql.exe Vcl.Controls TWinControl.MainWndProc 005dce43 heidisql.exe System.Classes StdWndProc 7ffb94be ntdll.dll KiUserCallbackDispatcher 7ffb93f6 USER32.dll PeekMessageW 008156bc heidisql.exe Vcl.Forms TApplication.ProcessMessage 00815833 heidisql.exe Vcl.Forms TApplication.HandleMessage 00815d1f heidisql.exe Vcl.Forms TApplication.Run 00cd4877 heidisql.exe heidisql 80 +24 initialization 7ffb9482 KERNEL32.DLL BaseThreadInitThunk 7ffb94bc ntdll.dll RtlUserThreadStart

lieszkol posted 2 months ago

I would like to second this. Heidi crashes once a day at least, and when it does I can't even recover what's in the editor. Super, super frustrating. It regularly happens when Heidi loses the connection and tries to reconnect in the background.

I'm not familiar with Delphi, but surely there must be some way to catch these exceptions and handle them without crashing the whole program. Or are these bugs coming from SynEdit and thus simply unavoidable? Could perhaps each window be run in a separate process, with a separate SynEdit instance, so that if SynEdit crashes in one of the editor windows it doesn't take all of the others down with it? Maybe it's a silly idea I'm just trying to think of ways to mitigate this. Why does losing the DB connection lead to the component in charge of syntax highlighting to crash, could these two aspects of the software be decoupled somehow?

If there is no hope for mitigation OK, let us know, and I'll bite the bullet and use some other editor, but the thing is I really like HeidiSQL (I've also donated my share). It has a great UI, I like the fact that each tab isn't using it's own DB connection, and it's so intuitive to use.

In any case thank you for all the work you put into Heidi.

1 attachment(s):
lemon_juice posted 2 months ago

I agree. Crashes are too common in Heidi and this makes me switch to other programs for most of database tasks. Heidi is a superb tool but the crashes are making it unusable sometimes.

I've submitted a few crash reports in the past as have other users but unfortunately Ansgar said he can't do anything about them because they are caused by some underlying platform or library that he has no control of. So I'm afraid that after all these years we may have to accept the crashes are here to stay forever...

The most frustrating ones are when I have multiple query tabs open and suddenly Heidi crashes when doing anything - there seems to be no repeatable pattern when they occur. And after restarting all my tabs with queries are lost, even no trace of them in query history. And sometimes Heidi just closes itself without warning when switching tabs or doing some other stuff and again, all queries lost upon restart.

At least a partial solution would be to implement some tab restore feature so that after restarting I can recover the queries. And every query should be saved to query history on disk immediately after pressing F9 just before running it.

To me this problems is big enough to warrant switching to another library/platform/language/whatever, because the otherwise wonderful application is ruined by the constant crashes. But that is probably only what we may hope for, for I understand how much work it would entail and Ansgar may simply not have enough time for this.

Please login to leave a reply, or register at first.