distal-attribute
distal-attribute
distal-attribute
distal-attribute

heidisql got really buggy

michaelgang posted 4 years ago in General
Hi,

I know that i work on a nightly build, but heidisql crashes on my computer every 5 minutes.
I am working on the nightly build of heidisql over 1 year and it rarely crashed. Is there a reason why i got unstable.
Will it be fixed in the soon future?

Thanks,
David
rashlin posted 4 years ago
i agree, there seems to be some issues with the multi-threaded queries...
still this still the best application for MYSQL so...

ansgar posted 4 years ago
Main reason is most probably the recently implementation of non blocking query threads. But I guess most of them are not different, will be fixed as soon as I spent further hours on that stuff.
Plasm posted 4 years ago
I agree as well. I like the new features (I don´t use MS SQL, but the threaded query tabs are great, for example), but I appreciate if most of the chrashes (and the no more executable tabs mentioned in another thread) will be fixed before any (bigger) new feature is added to HeidiSQL.
I meanwhile stopped reporting the crashes, since it really delays the workflow and I´m not sure, if it´s the same bug I already reported.
Especially annoying are the crashes when the "continue" button leads to another crash. Fortunately, HeidiSQL logs all user fired sql queries.
michaelgang posted 4 years ago
Hi,

The application is now much more stable.

Thanks a lot,
David
Steve06 posted 4 years ago
@Michaelgang:
I agree 100% and have been wondering myself if it's just my computer/server.
I use MySQL for data analysis and empirical research and have to save every query (most quite complex involving several joins) to a Word file just in case Heidi crashes which in fact happens every few minutes. (However, I just discovered recently that Microsoft OneNote is even better suited for organizing your queries semantically.)
And then I have to restart Heidi and copy/paste all queries back. By the way, that's also why I asked for some auto-save feature of the current environment, but first the bugs need to be eliminated.
Steve06 posted 4 years ago
@Michael: Contrarily to what you write in your recent post, I do not feel that HeidiSQL has gotten any more stable. I also use the latest build. It has become a habit of mine to check every day for a new build in hope the annoyances have been resolved - in vain, so far.
ansgar posted 4 years ago
If you experience crashes you should post them in the bug tracker or at least paste them here in the forum, before complaining about them.
michaelgang posted 4 years ago
My main problem is that i can not rproduce the problems. They occur occasionally. I can post the automatic generated crash reports but how will it help to solve these?
ansgar posted 4 years ago
Depends on the crash. Most crashes are reproducible if you have the callstack. But also in all other cases it's good to have it, as it offers some basic hint for the developer where to start searching in the myriad of code lines.
Steve06 posted 4 years ago
since the new build (3773) i haven't had any of the myriad of previous crashes. i don't know which of your fixes resolved the issue, but in any case: good job!
Steve06 posted 4 years ago
however, my co-worker just told me that she still experiences crashes after getting (involuntary) disconnected from the server, while trying to run a new query!
ansgar posted 4 years ago
Ok, then is there any chance I get the callstack from your co-worker?
Steve06 posted 4 years ago
i'll ask. how do you get the callstack? just click the save button when the error box pops up?
ansgar posted 4 years ago
Yes, the crash window has two tabs, the second one contains the callstack. Think there is a "Save to file" button somewhere on that dialog.
Curanai posted 4 years ago
Hi, sorry for this first posting, but "Houston, we have a problem!" ...

Currently "build 3773" is installed - ran properly yesterday. After updating the OS from Redmond after finishing the project I'm using heidisql with, today it should run, too ... but: no way!

Starting heidisql opens the normal connect-to screen - if mysql is running, no regular GUI opens ... if mysql isn't available, the "normal message" appears.

"compatibility mode" is not the right answer - already tried (OS: Win7-64; totally up-to-date; only the updates of the OS are the difference between "working"/"not working").

I can start multiple instances of heidisql ... the first five or six are round about 6.3 megabytes ... other ones are just 1.3 megabytes ... but: no GUI in no case!!

Well, it's Friday, customers are not amused and I have no GUI for working - any ideas?! (phpMyAdmin is also a "bad idea", but would be my second choice "in case of emergency").

Anyone with same viewings, problems or even a solution?! Many thanks ...
Curanai posted 4 years ago
Sorry, next feedback!! I just downloaded the portable version ... this one works fine. I guess "re-install" could be the solution ... *ahrg*
ansgar posted 4 years ago
Guess you have two screens? See issue #2372 for a workaround.
Curanai posted 4 years ago
Thanks for your replay, anse, but NO, only one display is in use and I haven't moved the GUI out of the viewable area. ;)

Normally HSQL is "really installed" - actually I have to use the portable one (still running; even after updating to 3773).
ansgar posted 4 years ago
I'd like to analyze this problem but could never reproduce it yet here. I'm sure this is due to some registry value for window dimension or positioning. Could you mail me a registry export of your HKEY_CURRENT_USER\Software\HeidiSQL\ key? You may want to delete server sub keys as these contain encrypted passwords for your servers. Mail link can be found at the very bottom of this page. Thanks a lot!
Curanai posted 4 years ago
Mail left the building ... thank you.
ansgar posted 4 years ago
Oh I think I have it. "windowstate" is "minimized" - this state is restored and tata - you have a process which does not show up because the values for windowleft and windowtop are invalid. Should be easy to fix.
ansgar posted 4 years ago
Hopefully all fixed in r3777.
Steve06 posted 4 years ago
anse,
i just experienced a similar crash to my co-worker: There was a disconnect and upon launching a new query, Heidi crashes. In this case I must add that I had to kill the query for taking excessively long via MySQL Workbench Administrator.

Here's the callstack:
date/time : 2011-04-16, 12:29:02, 674ms
computer name : xxx
user name : xxx <admin>
registered owner : Microsoft / Microsoft
operating system : Windows 7 x64 Service Pack 1 build 7601
system language : German
system up time : 3 days 9 hours
program up time : 2 days 10 hours
processors : 2x Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz
physical memory : 1196/4030 MB (free/total)
free disk space : (C:) 44,24 GB
display mode : 1440x900, 32 bit
process id : $1c6c
allocated memory : 75,61 MB
executable : heidisql.exe
exec. date/time : 2011-04-14 01:29
version : 6.0.0.3773
compiled with : Delphi XE
madExcept version : 3.0m beta 1
callstack crc : $cbffec66, $6ebf105c, $6ebf105c
exception number : 1
exception class : EAccessViolation
exception message : Access violation at address 1000BDFA in module 'libmysql.dll'. Read of address 00000358.

main thread ($1e84):
1000bdfa libmysql.dll mysql_send_query
1000bea0 libmysql.dll mysql_real_query
0073e561 heidisql.exe dbconnection 1276 +20 TMySQLConnection.Query
00746ee4 heidisql.exe dbconnection 3130 +3 TMySQLQuery.Execute
0074060d heidisql.exe dbconnection 1735 +5 TDBConnection.GetResults
007415d0 heidisql.exe dbconnection 2024 +3 TMySQLConnection.GetCollationTable
00744c0a heidisql.exe dbconnection 2727 +80 TDBConnection.ParseTableStructure
007d6b6a heidisql.exe Main 4591 +18 addColumns
007d72d0 heidisql.exe Main 4707 +102 TMainForm.SynCompletionProposalExecute
00657a6e heidisql.exe SynCompletionProposal 2437 +5 TSynBaseCompletionProposal.ExecuteEx
0065909b heidisql.exe SynCompletionProposal 3267 +5 TSynCompletionProposal.ExecuteEx
0065929f heidisql.exe SynCompletionProposal 3350 +18 TSynCompletionProposal.DoExecute
00658f90 heidisql.exe SynCompletionProposal 3221 +5 TSynCompletionProposal.TimerExecute
0053595f heidisql.exe ExtCtrls TTimer.Timer
00535843 heidisql.exe ExtCtrls TTimer.WndProc
004aaff4 heidisql.exe Classes StdWndProc
75a37885 USER32.dll DispatchMessageW
00586cfb heidisql.exe Forms TApplication.ProcessMessage
00586d3e heidisql.exe Forms TApplication.HandleMessage
00587069 heidisql.exe Forms TApplication.Run
007f989f heidisql.exe heidisql 66 +16 initialization
74ac33c8 kernel32.dll BaseThreadInitThunk
Steve06 posted 4 years ago
anse, just had the same crash again, and this time it wasn't after killing the query. The connection was closed involuntarily.
ansgar posted 4 years ago
Hm I am not able to reproduce that here, when I have a disconnected session and opening the completion proposal. Can you tell me how to reproduce this?
Steve06 posted 4 years ago
just launch a query that takes long enough to give you the time to kill it "brute-force" externally via some MySQL admin tool (MySQL Administrator or MySQL Workbench, for example).
The error also occurs on involuntary "connection closes", but these are harder to reproduce.
Curanai posted 4 years ago
Hi again,

because of the "problem", I can't update the 'installed' version of HSQL (external updater?!), so I just set "maximized" to the "windowstate" (registry) and *tada* ... opens up! The values of 'windowleft' and 'windowtop' weren't changed ...

So, next was trouble while updating to r3779. "no response" (window) while 'Closing "Session manager' (second quote missing) ... no update taken, after window disappeard! Tried it now six or seven times ... including restarting (HSQL) and so on. Finally, the update was installed, because of closing the application manually, while the window is in "no response". But this could be a "system thing" ... now, everything is up-to-date, viewable and back in productivity.

Thanx ... I'm happy again! ;)

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