Bug #116134 MySQL Workbench 8 - Result Grid too slow to load and navigate.

Description:
I just got a fresh new computer and installed MySQL Workbench, which I have been using daily for many years, always up to date, but now it seems to process Result Grid very badly.

When I execute a SELECT query, the results are not shown instantly in screen. Instead, it loads line by line, like if I was running it on a very old computer.  The action is already done (eg: 0.125 sec), but the Result Grid takes about 1 second to finish the listing. It also happens when I roll the scrollbar, resize the window or create new rows directly in Result Grid.

Look, I was using the same [i5 / 16GB RAM / 1GB GPU / Windows 10] computer for about 12 years, and now I got a [i7 / 32GB RAM / 8GB RTX4060 GPU / Windows 11].

How to repeat:
Just try to do anything when Result Grid is on screen.

Hello Rafael rzgons,

Thank you for the report and feedback.
I have tried to reproduce this on MacOS with remote MySQL Server instance and fetching million rows - it took a while to fetch data but there was no issues observed while navigating rows by rows. Checked with a colleague of mine who was using Workbench on Windows 11 but no issues observed there as well.

To investigate further this issue at our end, may I kindly request you
to launch workbench under debug mode (--log-level=debug3) and provide
unaltered workbench log file(more details about log are explained here -
https://dev.mysql.com/doc/workbench/en/workbench-reporting-bugs.html) along with screenshot of the problem? Thank you.

regards,
Umesh

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".

Thank you for the feedback.

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.