| Bug #82072 | MySQL Workbench closes when executing queries in large tables on remote servers | ||
|---|---|---|---|
| Submitted: | 30 Jun 2016 21:11 | Modified: | 5 Aug 2016 16:26 | 
| Reporter: | Cristian Umaña | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Workbench: SQL Editor | Severity: | S1 (Critical) | 
| Version: | 6.3.7 | OS: | Linux (Ubuntu 16.04 LTS) | 
| Assigned to: | CPU Architecture: | Any | |
| Tags: | 6.3.7, WBBugReporter, workbench | ||
   [3 Aug 2016 6:12]
   MySQL Verification Team        
  Thank you for the details. This reminds me of Bug #81972, but cannot confirm since no back trace etc I would suggest you to launch WB with --log-level=debug3 option and see if this helps. See https://dev.mysql.com/doc/workbench/en/workbench-reporting-bugs.html Thanks, Umesh
   [3 Aug 2016 19:57]
   Cristian Umaña        
  Hi Umesh, thank you for your time too. I read: https://dev.mysql.com/doc/workbench/en/workbench-reporting-bugs.html And following the steps there I uploaded two files in this report that "only developers will be able to see the file" I hoping is what you need Regards.
   [5 Aug 2016 8:47]
   MySQL Verification Team        
  Thank you Cristian Umaña. This reminds me of Bug #81972, most likely duplicate of Bug #81972. Thanks, Umesh
   [5 Aug 2016 16:26]
   Cristian Umaña        
  Hi Umesh, Great but only one observation on Bug #81972, it's marked as S3 and there isn't a workaround, IMHO Bug #81972 severity must be switch to S1. What do you think? Regards,


Description: MySQL Workbench closes inmediately without hang when executing queries that take some time or when use distinct clause on large tables. This happens when I connected to remote servers. How to repeat: - Connect to a remote server - try distinct statement on a large table: select distinct {column} from {large_table} - try count statement on a large table: select count(1) from {large_table} Suggested fix: On previous versions it worked fine, so, maybe is a recent change. Regards