Page 1 of 1

Memory Leak

Posted: Thu 19 Jul 2012 17:41
by dschoof
Hi,
I've found a major memory leak in SQL Complete for Sql Server, which requires me to restart SSMS quite frequently. The time varies, but sometimes SSMS memory usage grows to 1 GB within a few minutes, if I work on large enough files.

I frequently work with large files (~3000 lines or more) with very similar layout, and these seem to cause issues for SQL Complete. The format of these files is as follows:

Code: Select all

SET IDENTITY_INSERT Table1 ON;
INSERT INTO Table1 (Column1, Column2, ...)
SELECT Column1, Column2, ... FROM (
SELECT Value1_1, Value2_1, ... UNION ALL
SELECT Value1_2, Value2_2, ... UNION ALL
...
SELECT Value1_2999, Value2_2999, ... )
t (Column1, Column 2, ...)
WHERE NOT EXISTS (SELECT * FROM Table1 t1 WHERE t1.Column1 = t.Column1);
SET IDENTITY_INSERT Table1 OFF;
Could you please look into this and provide a solution for this issue? It does make SQL Complete somewhat unusable for these files, since it also becomes very slow and I frequently lose work from crashes while editing the files.

Re: Memory Leak

Posted: Fri 20 Jul 2012 10:32
by alexa
Please check and confirm that you are using the latest version 3.5.72: http://www.devart.com/dbforge/sql/sqlco ... nload.html

Re: Memory Leak

Posted: Fri 20 Jul 2012 12:22
by dschoof
Yes, I am using the latest version. I have noticed this kind of problem since I began using the free version a while ago, and then also with the trial and now the full version. This means that a similar leak has been in there since version 3.5.60 (when I started using the free version).

Do you have anything I can do / run to get you more information on this?

Just to confirm that it was SQL Complete that caused this memory leak (I also have SSMS Tools pack installed, but have run in the past without it), I uninstalled SQL Complete and then did the same work as before. Without SQL Complete, the memory usage stayed below 200MB.

Re: Memory Leak

Posted: Fri 20 Jul 2012 12:57
by alexa
Thank you for the reply.

Could you please also send us the complete SQL file to supportATdevartDOTcom for further investigation?

Re: Memory Leak

Posted: Wed 12 Sep 2012 16:42
by alexa
We would like to let you know that the new build 3.5.83 of dbForge SQL Complete, where the issue you reported is fixed, has been released and is available for downloading: http://www.devart.com/dbforge/sql/sqlco ... nload.html

Thank you for your help in improving dbForge SQL Complete.

Re: Memory Leak

Posted: Thu 20 Sep 2012 14:40
by doreladam
The problem seems to be related to the Visual Studio/SQL Server Management Studio option Text Editor\Transact-SQL\IntelliSense\Enable IntelliSense. In the case of large files the memory leak exists and the environment eventually crashes even with SQL Complete uninstalled if the Enable IntelliSense option is enabled.

Unfortunately this workaround disables Underline errors and Outline statements, which for large files is quite invaluable.

Re: Memory Leak

Posted: Thu 20 Sep 2012 14:49
by dschoof
Perhaps it would be possible for SQL Complete to start providing this functionality instead, to replace the existing SSMS functionality in this area?

I would love to see SQL Complete become the "ReSharper" of SQL, checking for unused variables, errors, etc.