Bug #75182 Unhandled Exception resultNextRow() Invalid resultset

• Submitted: 11 Dec 2014 14:48
• Modified: 29 Dec 2014 5:28
• Reporter: Miguel Espinoza
• Status: Can't repeat
• Category: MySQL Workbench
• Severity: S3 (Non-critical)
• Version: 6.2.4
• OS: MacOS
• CPU Architecture: Any

[11 Dec 2014 14:48] Miguel Espinoza

Description:
I have 3 connections open to 3 different servers. I was examining a long query with explain, then I went to another window (Google Chrome), I did not close nor minimise MySQL Workbench, I just clicked on the Google Chrome icon to bring it to front. Possibly the Client Connections tab was running.

After a couple of minutes, and while still in Google Chrome, the following alert popped up:

Unhandled exception: DbMySQLQuery.resultNextRow(): Invalid resultset

How to repeat:
1- Use MySQL Workbench
2- Go to another program without closing Workbench
3- Randomly, the error alert will show.

A colleague tells me that it also happens sometimes when killing a query from the Client Connections tab, so it is possibly related to this feature.

[11 Dec 2014 14:49] Miguel Espinoza

Screenshot of the alert pop up

Attachment: Screen Shot 2014-12-11 at 15.42.56.png (image/png, text), 14.81 KiB.

[11 Dec 2014 17:26] MySQL Verification Team

Please check with version 6.2.4. Thanks.

[12 Dec 2014 8:08] Miguel Espinoza

I have another "bug" then, going to the "Help" menu and clicking "Check for update" says Im already using the latest version, but going to the website I found there was in fact a newer version (6.2.4). 

I have downloaded 6.2.4 and will be keeping an eye out for this, if I see it happen then I'll come back to this report.

Thanks

[14 Dec 2014 21:35] MySQL Verification Team

Thank you for the feedback. So the Unhandled Exception isn't more repeatable on 6.2.4? the update issue was already reported. Thanks.

[19 Dec 2014 8:36] Miguel Espinoza

Well I have been sparingly using it this week and have not run into it any more

[29 Dec 2014 5:28] MySQL Verification Team

Thank you for the feedback and confirmation.
If you are able to reproduce the bug with one of the latest versions, please change the version on this bug report to the version you tested and change the status back to "Open".  Again, thank you for your continued support of MySQL.

Thanks,
Umesh

[18 Feb 2019 17:11] Priyesh Agarwal

Hi ,
Facing the same issue in Version 6.3.9

Can you please help me?

[21 Feb 2019 14:49] Priyesh Agarwal

My OS is Windows 10 x64 I am getting the same error.
Can you please help me?

[26 Mar 2019 14:49] Priyesh Agarwal

Is there any update on this issue?