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

Bug: Memory violation after server disconnect

beast_drc posted 5 months ago in General

Hi I'm using mysql server on vmWare machine. Heidi connected to the server via SSH tunnel. when SSH connection closing, Heidi shows an error instead of trying to reconnect it's very annoying bug, aspecial when you have open tabs with queries. As i know this bug presents for 3 or 4 years.

1 attachment(s):
ansgar posted 5 months ago

Should be fixed in r5164. Please update HeidiSQL to the latest build and report back here if the problem persists.

beast_drc posted 5 months ago

Hi! better, but not ideal. Steps to reproduce:

  1. heidi connected
  2. stop server
  3. refresh db list -> crash after 2 or 3 attempts (bugreport1)
  4. click Continue application (bugreport2)
  5. click continue - bug report window gone
  6. start server
  7. update ->crash (bugreport3)
  8. continue (2 times), bug report window gone
  9. then reconnect is ok. (previously you can press continue infinitly and no effect) Thanks for fix
3 attachment(s):
beast_drc posted 5 months ago

BTW nl2br would be good here :)

ansgar posted 5 months ago

You just need to use dots after line numbers to generate a real ol-list. See any Markdown documentation.

beast_drc posted 5 months ago

Hi! Thanks for the release. just tested.. problem persists. heidi tries to reconnect after several attempts crash. i rerun the server and can't close bugreport window. it infinitely reappear until "Continue application" become disabled

3 attachment(s):
ansgar posted 5 months ago

So the server is not connectable after the disconnect, is that right? If so, a reconnect cannot be done and should probably be tried 2 or 3 times, but after that the session should just close in HeidiSQL, just as if you have closed it manually. Right?

beast_drc posted 5 months ago

Hi. After several attempts it crashes, but not closes. I think normal behavior is show error message, and ask user for manual connection. I reproduces it synthetically, but, it is normal, for example when you are using Mobile Internet. Program should wait either reconnecting or closing manually with saving all queries from open tabs.

ansgar posted 5 months ago

Yes I think I should just close the connection in such cases, and show the session manager if no active session is left. In case there is a second or third active session, there is no need to show the session manager.

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