UI freezes/crashes when selecting or editing a cell with large data in Data tab

homliangwu's profile image homliangwu posted 3 months ago in General Permalink

Summary

When viewing a table with large cell contents (e.g., long JSON, large TEXT/LONGTEXT or BLOB), clicking/selecting or attempting to edit an individual cell in the Data tab causes HeidiSQL to freeze permanently (Not Responding) and requires a force close.

Steps to Reproduce

  1. Connect to a database containing a table with large cell contents (e.g., text > a few MBs or huge single-line strings).
  2. Open the Data tab and locate the row with the large data.
  3. Click or double-click the cell containing the large value.

Expected Behavior

The UI should remain responsive. The application should either truncate the preview inline, load content asynchronously, or prompt before loading/rendering the entire large text into the editor component.

Actual Behavior

The entire HeidiSQL GUI freezes completely (Windows reports "Not Responding") and memory/CPU usage spikes, forcing the user to kill the process via Task Manager.

Environment

  • HeidiSQL Version: [e.g., 12.8.0.6900 / 64-bit] (Help -> About HeidiSQL)
  • OS: Windows 11 (x64)
  • Database Server / Version: [e.g., MySQL 8.0 / MariaDB 10.x]
  • Approximate Data Size / Column Type: [e.g., LONGTEXT / ~5MB JSON string]

Additional Context

  • The issue occurs when HeidiSQL attempts to load and render the raw string in the grid cell / text editor panel.
gary.futch66's profile image gary.futch66 posted 1 month ago Permalink

This sounds more like the cell editor trying to load the entire value into memory than a MySQL problem itself. A few MB of JSON/text is enough to make a grid/editor component struggle, especially if it is trying to format or render the whole string synchronously.

As a workaround, I’d avoid double-clicking those large fields from the Data tab and use a query with LEFT()/SUBSTRING() to inspect only part of the value, for example:

SELECT id, LEFT(large_column, 10000)
FROM your_table
WHERE id = ...;

It would also be worth testing the same table with a smaller value to confirm the freeze is directly related to the field size. If the application becomes unresponsive only when opening the large cell, that gives the developers a pretty clear reproduction case.

If the large fields are from a database that has already suffered corruption and the goal is to recover the actual MySQL data rather than just inspect it in HeidiSQL, a recovery tool such as Stellar Repair for MySQL is another option worth considering. I wouldn't use it as a workaround for the HeidiSQL freeze itself, though—the underlying issue here still looks like how HeidiSQL handles very large cell contents.

homliangwu's profile image homliangwu posted 4 weeks ago Permalink

Alright, I've already done it.

Please login to leave a reply, or register at first.