Bug: selecting a table in the tree causes tabs not to work

[expired user #5286]'s profile image [expired user #5286] posted 13 years ago in General Permalink
Steps to reproduce:
1) Open connection;
2) Expand tree;
3) click on a table in the tree;
4) clicking a tab (eg. query) causes a access violation.

If I click on the database name, then click the query tab, then click on a table name, it works fine.

I'm running latest beta Heidi under Wine on Ubuntu 10.10.

Below is the bug report generated by Heidi:

date/time : 2010-11-11, 10:47:05, 795ms

computer name : cameron

user name : cameron <admin>

registered owner : Change preferred owner in ~/.wine/system.reg / Change preferred organization in ~/.wine/system.reg

operating system : Windows XP Service Pack 2 build 2600

system language : English

system up time : 1 hour 51 minutes

program up time : 2 minutes 52 seconds

physical memory : 2594/3529 MB (free/total)

free disk space : (C:) 37.01 GB

display mode : 1920x1200, 32 bit

process id : $36

allocated memory : 19.64 MB

executable : heidisql.exe

exec. date/time : 2010-11-11 08:58

version : 5.1.0.3584

compiled with : Delphi 2010

madExcept version : 3.0k

callstack crc : $62ce0cab, $440df25c, $440df25c

exception number : 6

exception class : EAccessViolation

exception message : Access violation at address 004FCE18 in module 'heidisql.exe'. Read of address 00000274.



main thread ($37):

004fce18 heidisql.exe ComCtrls TTabSheet.GetPageIndex

006c819a heidisql.exe Main 4138 +11 TMainForm.PageControlMainChange

004fbe95 heidisql.exe ComCtrls TCustomTabControl.Change

004fd519 heidisql.exe ComCtrls TPageControl.Change

004fc951 heidisql.exe ComCtrls TCustomTabControl.CNNotify

0053ab60 heidisql.exe Controls TControl.WndProc

0053f428 heidisql.exe Controls TWinControl.WndProc

7b82642e KERNEL32.dll GlobalFindAtomW

0053a784 heidisql.exe Controls TControl.Perform

0053f57b heidisql.exe Controls DoControlMsg

00540005 heidisql.exe Controls TWinControl.WMNotify

0053ab60 heidisql.exe Controls TControl.WndProc

0053f428 heidisql.exe Controls TWinControl.WndProc

0053eac8 heidisql.exe Controls TWinControl.MainWndProc

0049a524 heidisql.exe Classes StdWndProc

684f8847 user32.dll SendMessageW

0053ab60 heidisql.exe Controls TControl.WndProc

6852ffd5 user32.dll CallWindowProcW

0053f528 heidisql.exe Controls TWinControl.DefaultHandler

0053b1dd heidisql.exe Controls TControl.WMLButtonDown

004fe071 heidisql.exe ComCtrls TPageControl.WMLButtonDown

0053ab60 heidisql.exe Controls TControl.WndProc

0053f428 heidisql.exe Controls TWinControl.WndProc

0053eac8 heidisql.exe Controls TWinControl.MainWndProc

0049a524 heidisql.exe Classes StdWndProc

684f3e19 user32.dll DispatchMessageW

0056b229 heidisql.exe Forms TApplication.ProcessMessage

0056b26e heidisql.exe Forms TApplication.HandleMessage

0056b599 heidisql.exe Forms TApplication.Run

007a7742 heidisql.exe heidisql 66 +15 initialization

7bc6e8bb ntdll.dll RtlExitUserThread
ansgar's profile image ansgar posted 13 years ago Permalink
This is a known proble in Wine, see issue #2227. Nothing I can do about that, unfortunately, as this is Wine specific.
[expired user #5286]'s profile image [expired user #5286] posted 13 years ago Permalink
Thanks, I only found it after updating to the latest beta (build 5.1.0.3584).
ansgar's profile image ansgar posted 13 years ago Permalink
Probably also related: issue #2093. See the hint with "Wine MS Windows Compatibility Layer (Beta Release)".
ansgar's profile image ansgar posted 13 years ago Permalink
From which one did you update, then? Probably there was some Wine incompatible code change in HeidiSQL, but I need to know which revision it was or at least roughly.
[expired user #5286]'s profile image [expired user #5286] posted 13 years ago Permalink
r3574 or so I think. Not 100% sure. I wonder if it's the update to the VirtualTree component?
ansgar's profile image ansgar posted 13 years ago Permalink
Thanks, will check that. But no, cannot be the move to VT, as that was done much earlier.
ansgar's profile image ansgar posted 13 years ago Permalink
The cause was most probably r3578. Could you please check again, after updating to r3586?
ansgar's profile image ansgar posted 13 years ago Permalink
eh... better take r3587, please.
[expired user #5286]'s profile image [expired user #5286] posted 13 years ago Permalink
Just updated to r3590 and the issue has gone. Much appreciated!
ansgar's profile image ansgar posted 13 years ago Permalink
Yes, a colleague at work already confirmed that. Means, Wine does not activate a tabsheet when its tab is hidden. This is different as on Windows so it could be named a Wine bug. On the other hand this is easy to work around in the application side, which I did in r3586.

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