Bug #118683 MySQL Workbench throws “Index was out of range” error after running stored procedure and using Filter Rows

• Submitted: 18 Jul 12:05
• Modified: 18 Jul 13:01
• Reporter: Sudarshan Parkale
• Status: Can't repeat
• Category: MySQL Workbench: SQL Editor
• Severity: S2 (Serious)
• Version: 8.0.34
• OS: Windows (11)
• CPU Architecture: Any
• Tags: crash, exception, Filter Rows, stored procedure, UI bug, workbench

[18 Jul 12:05] Sudarshan Parkale

Description:
After executing a stored procedure using the CALL statement, MySQL Workbench crashes when attempting to use the "Filter Rows" option in the result grid. The specific error shown is:

Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

The stored procedure that triggered this was:
CALL gdb0041.top_market_by_net_sales(2021,1);

After the result grid was displayed, I clicked on the "Filter Rows" box and entered the column name net_sales_min. Upon pressing Enter or navigating away, Workbench immediately crashed with the above error message.

This appears to be a UI bug in the Filter Rows handler when used with stored procedure result sets.

How to repeat:
Open MySQL Workbench (v8.0.x)

Execute the stored procedure:
CALL gdb0041.top_market_by_net_sales(2021,1);

After the result grid loads, click the Filter Rows box (above the column headers).

Enter a column name (e.g., net_sales_min) without completing an expression.

Workbench throws an error:
"Index was out of range. Must be non-negative and less than the size of the collection."

it throws error after this query showed result but it still in running state and i was not able to close workbench also.

Suggested fix:
Improve error handling for result grid filtering.

Add validation to check the presence and structure of columns after CALL queries.

Prevent filter box from triggering internal index errors on stored procedure results.

[18 Jul 13:01] MySQL Verification Team

Hello Sudarshan,

Thank you for the bug report.
I tried to reproduce your issue on windows 11 with workbench 8.0.42 using dummy stored procedure but I am not seeing any issues at my end.
Please upgrade to latest version and try again.

Regards,
Ashwini Patil