Running Queries or viewing large tables crashes application

[jordonbrill]

1. Which driver are you using and version of it (Ex: PostgreSQL 10.0): MySQL 5.7.25 Ubuntu 18.04.2

2. Which TablePlus build number are you using (the number on the welcome screen, Ex: build 81): Build 62

3. The steps to reproduce this issue:
   Run simple select where query on table of about 40,000 or just open large table and the application shuts down. I don't seem to be getting an error message or anything - the application just closes. Happy to help diagnose further!

Noted: If the bug is related to data, please attach an example SQL data.

[huyphams]

Thank you @jordonbrill for the feedback, let me check it.

[jordonbrill]

Is there anything you would like me to help with on this?

[huyphams]

Thank you for reminding me, I've checked multiple times, but I don't think it's related to the number of rows, I think it's related to the data parsing. This issue still occurring on the build 66?

[jordonbrill]

The issue does still exist in the latest version even though I'm not 100% clear on what the issue actually is. I'm not really sure what's going on. I tried viewing one of my tables (which has a pretty simple structure and no real strange data) and it still just randomly closes the application. Here's the structure of one of the tables:

CREATE TABLE `tablename` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `app` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL,
  `authentication` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
  `ip` varchar(45) COLLATE utf8_unicode_ci NOT NULL,
  `params` mediumtext COLLATE utf8_unicode_ci NOT NULL,
  `route` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
  `status_code` int(11) NOT NULL,
  `created_at` timestamp NULL DEFAULT NULL,
  `updated_at` timestamp NULL DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci

It closes when I query it and also when I just click next page of results

I did run this query

select count(*), app from tablename group by app;

and it didn't crash but actually showed me results after a while. The table has about 6.5M rows. Odd. Perhaps it is related to parsing/display of the data somehow - because this just showed summary data and worked.

[jordonbrill]

Major kudos to the team. I have been installing the updates that have been coming out (quite frequently, which is AWESOME) and the product continues to be much better. This problem appears to be resolved now. Thank you!