MySQL Bugs: #76867: Getting sql editor window crossed by a red lines

Bug #76867	Getting sql editor window crossed by a red lines
Submitted:	28 Apr 2015 11:31	Modified:	30 May 2015 10:08
Reporter:	Manula Madushanka	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	6.9.6	OS:	Windows (8.0)
Assigned to:		CPU Architecture:	Any
Tags:	MySQL

Description:
It is getting a red crossed sql query editor window for many times. When I am working with a queries I had this issue soo many times and I have to restart work bench many times. And my changes ot SPs and sql queries get lost.

How to repeat:
I got the same cross window for several times per day. When I am scripting for SP and executing, even table rows executing the query window get freezes and can not execute them anymore.
 

Suggested fix:
no idea why that is getting

Thank you for the bug report. Please attach a screenshot of the issue and the output of Help->System Info of WorkBench. Thanks.

Hi,

Here is the System infor for work bench :

MySQL Workbench Community (GPL) for Windows version 6.1.6  revision 11834 build 1642
Configuration Directory: C:\Users\manula\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench CE 6.1.6
Cairo Version: 1.8.8
OS: Microsoft  (build 9200), 64-bit
CPU: 4x Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz, 3.9 GiB RAM
Active video adapter Intel(R) HD Graphics 4000
Installed video RAM: 1812 MB
Current video mode: 1366 x 768 x 4294967296 colors
Used bit depth: 32
Driver version: 10.18.10.3412
Installed display drivers: igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igdumdim32,igd10iumd32,igd10iumd32
Current user language: English (United States)

An sreen shot of mysql bug

Attachment: MySQL BUG.png (image/png, text), 38.58 KiB.

This is actually what I have in editor when error gets.

Attachment: MySQL BUG 2.png (image/png, text), 70.74 KiB.

Thank you for the feedback. Your WorkBench version is quite older (6.1.6) please try the new version 6.3.3. Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".