MySQL Bugs: #4503: memory access violations and tabsheets

Bug #4503	memory access violations and tabsheets
Submitted:	10 Jul 2004 18:13	Modified:	14 Jul 2004 10:43
Reporter:	Alistair Maclean	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S2 (Serious)
Version:	1.0.2 alpha	OS:	Windows (Windows 2000 Pro)
Assigned to:	Michael G. Zinner	CPU Architecture:	Any

Description:
Memory access violations when using tabsheets. Selection of new tabsheets and their deletion leading to unstable operation.

How to repeat:
Open application
Go File | New | Tabsheet and open a new tabsheet (2 tabsheets on screen, called tabsheet 1 and tabsheet 2)
Select tabsheet 1
Close tabsheet 1 (using red folder closing icon at top right of grid)
Attempt to do anything else leads to memory access violations 
Some of which are reading memory at address 0, others look like valid addresses - "Access violation at address 0040FD94 in module MySQLQueryBrowser.exe. Read of Address 000000B0."

Occasionally, I can get the system to work again. At which point you can create new tabsheets, but the first of which is again called tabsheet 2, you now have 2 tabsheet 2's). Loading these with queries and deleting the first sheet leads to some very odd tab removals. Sometimes it will remove the current tab, other times it will remove the background tab. This evidences it self as the wrong query results remaining on screen. 

Suggested fix:
The tabsheet manager needs some re-organisation.
There may be some graphical redraw issues as well (tabs being Ok but not being redrawn as changes occur)

I only was able to repeat the 2 tabsheet2 behavior without the
memory access violation.

Thanks

Thanks for your detailed bug report! There has been some messup in the tab deletion code which has now been fixed. The bugfix is available in the source repository and will be in the next release.