Bug #103560 "Index was out of range" when closing tab during right-most tab's running query
| Submitted: | 3 May 2021 17:02 | Modified: | 3 May 2021 18:42 |
|---|---|---|---|
| Reporter: | Jason Brunette | Email Updates: | |
| Status: | Won't Fix | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
| Version: | 8.0.24 | OS: | Windows |
| Assigned to: | CPU Architecture: | Any |
[3 May 2021 17:02]
Jason Brunette
[3 May 2021 18:42]
MySQL Verification Team
Thank you for the bug report.
[22 Sep 2022 15:05]
Brian Jones
Similar situation. Ran query on final tab on workbench, then closed next tab to the left, which triggered the error.
[16 May 2023 23:26]
Ed Critz
I had close to the same problem and can replicate what happened. I have multiple tabs open. I execute the next to last tab, and while it is running I save and then close the last tab. Workbench did not immediately fail and present an error. 2 - 3 seconds after clicking to execute the query, I switched to another full-screen program. When I went back to Workbench to check the query results, I encountered the error window "MySQL Workbench has encountered a problem Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index". I think I understand what might be causing this problem and others reported about managing tabs, primarily closing one or more, while there is a tab waiting for the results of an active query. I would very much like to assist in resolving this but it would be the first time in over 10 years that I have worked on an open-source project. It would probably be like doing it for the first time. Point me to a link showing what I would need to do to get involved. I think the open-source would be a good place to wind down a multi-century career.
[14 Sep 18:06]
Omer Barnir
Posted by developer: This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained. MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation. Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.061 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.