New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heidi crashing on Foreign Key creation #473

Closed
stigzler opened this Issue Jan 6, 2019 · 6 comments

Comments

Projects
None yet
2 participants
@stigzler
Copy link

stigzler commented Jan 6, 2019

date/time          : 2019-01-06, 18:49:59, 330ms
computer name      : HPSERVER
wts client name    : BLACKKNIGHT2
user name          : Administrator <admin>
registered owner   : Administrator
operating system   : Windows 2008 R2 x64 Service Pack 1 build 7601
system language    : English
system up time     : 1 day 15 hours
program up time    : 33 seconds
processors         : 4x Intel(R) Xeon(R) CPU E3-1225 v3 @ 3.20GHz
physical memory    : 1957/8100 MB (free/total)
free disk space    : (C:) 450.80 GB
display mode       : 1920x1080, 32 bit
process id         : $2918
allocated memory   : 62.13 MB
largest free block : 8181.38 GB
executable         : heidisql.exe
exec. date/time    : 2019-01-06 10:56
version            : 9.5.0.5440
compiled with      : Delphi 10.3 Rio
madExcept version  : 5.0.0
callstack crc      : $321d0205, $47c8353d, $47c8353d
exception number   : 1
exception class    : EAccessViolation
exception message  : Access violation at address 00000000006A8222 in module 'heidisql.exe'. Read of address 0000000000000010.

main thread ($2734):
006a8222 heidisql.exe Vcl.Controls          TWinControl.WndProc
006d8dd0 heidisql.exe Vcl.StdCtrls          TButtonControl.WndProc
006a78da heidisql.exe Vcl.Controls          TWinControl.MainWndProc
0055c293 heidisql.exe System.Classes        StdWndProc
76ca98bd USER32.dll                         DispatchMessageW
0084e07e heidisql.exe Vcl.Forms             TApplication.ProcessMessage
0084e0f3 heidisql.exe Vcl.Forms             TApplication.HandleMessage
0084e541 heidisql.exe Vcl.Forms             TApplication.Run
00dd6cba heidisql.exe heidisql       85 +26 initialization
76da59cb kernel32.dll                       BaseThreadInitThunk
76f0383b ntdll.dll                          RtlUserThreadStart

Steps to reproduce this issue

  1. Step 1; Start a new foreign key on a table
  2. Step 2; Select field from "Column"
  3. Step N;
  4. Then I get... That crash report + Heidi malfunctions

Current behavior

Expected behavior

Possible solution

Environment

  • HeidiSQL version: Revision 5442 (yours: 5442)

@ansgarbecker ansgarbecker added this to the v10 milestone Jan 6, 2019

@stigzler

This comment has been minimized.

Copy link
Author

stigzler commented Jan 6, 2019

For info: Reverted to Rev 5196 and not an issue there.
btw - love that DarkTheme - very nicely done.

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

ansgarbecker commented Jan 6, 2019

I have that crash only when I selected a non-default theme. With the default Windows theme and the latest nightly build I get no crash.
Can you confirm that?

@stigzler

This comment has been minimized.

Copy link
Author

stigzler commented Jan 6, 2019

Yes - works fine on latest nightly with Theme "Windows"

@ansgarbecker ansgarbecker added themes and removed question labels Jan 7, 2019

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

ansgarbecker commented Jan 7, 2019

Thanks for verifying that. Hope I can fix that. These themes crash a bit too often in my eyes.

@stigzler

This comment has been minimized.

Copy link
Author

stigzler commented Jan 7, 2019

Thanks, man. Don't bail too early on those themes - they look awesome + dark theme is a must these days. However, hearing the pain of aesthetics affecting solid code ;)

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

ansgarbecker commented Jan 8, 2019

I'm hesitating with the v10 release now that I see some theme related crashes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment