| Bug #80585 | Memory leak in administration - Client connections | ||
|---|---|---|---|
| Submitted: | 2 Mar 2016 13:11 | Modified: | 23 May 2016 11:48 | 
| Reporter: | Fredric Johansson | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S3 (Non-critical) | 
| Version: | 6.3.6 | OS: | Windows | 
| Assigned to: | CPU Architecture: | Any | |
   [2 Mar 2016 13:11]
   Fredric Johansson        
  
 
   [4 Mar 2016 16:14]
   MySQL Verification Team        
  memory used while querying a big table ~9 GB
Attachment: memory.png (image/png, text), 30.78 KiB.
   [4 Mar 2016 16:15]
   MySQL Verification Team        
  memory released after the big result set was fecthed
Attachment: memory_released.png (image/png, text), 79.40 KiB.
   [4 Mar 2016 16:19]
   MySQL Verification Team        
  Thank you for the bug report. I added 2 pictures: first one memory used while running a big query around 9 GB and the second one showing the memory was released by WorkBench after the query was finalized. So where is the memory leak?. Please check on your side too. Thanks.
   [8 Mar 2016 17:04]
   Fredric Johansson        
  I noticed it when connecting to a server over ssh but cant reproduce it when running against a local server
   [8 Mar 2016 18:15]
   Fredric Johansson        
  During an import the memory does not appear to go up when long-running queries like ALTER TABLE run, but goes up while INSERTs are running

