LinqConnect Professional Version 4.4.453 (06-Mar-2014) - Memory Leak

[AKRRKA]

Thank you.
Really looking forward. For me, it is very critical.

Tell me please, can turn off caching?
What is the general sense and usefulness of this cache?
I was more than satisfied if the requests are simply relayed to the database without using the cache.

[MariiaI]

Tell me please, can turn off caching?
What is the general sense and usefulness of this cache?

For more information about caching please refer to:
http://www.devart.com/linqconnect/docs/ ... eries.html

You can disable the use of compiled query cache. For example, open the properties of the used template "LinqConnect" (select Properties from the template's context menu in the Model Explorer -> Templates), set "Use Compiled Query Cache" to False and save the changes to regenerate the *.Designer.cs file.

For more information about entity cache and Entity Cache Modes, please refer to http://www.devart.com/linqconnect/docs/ ... ntity.html
To disable entity cache, you can use this code:

Code: Select all

YourDataContext ctx = new YourDataContext();
ctx.EntityCachingMode = EntityCachingMode.None;

If you have any further questions, feel free to contact us.

[AKRRKA]

Thanks for the information.

But I had already tried different modes for properties EntityCachingMode, including the None. And in all cases was a memory leak.

And now tried to disable "Use Compiled Query Cache" in the file * .Designer.cs, but it did not change anything, a memory leak has remained the same.

You can try to do it on my example and you will see that the memory leak still remains.

[MariiaI]

Thank you for the response. We will contact you as soon as possible.

[AKRRKA]

How is the investigation? Any news?

[MariiaI]

Sorry for the delay. The investigation is in progress.
Currently, the memory leak errors do not occur in our environment with the latest build of LinqConnect 4.4.621. We have tested both your projects.
Please try the latest LinqConnect 4.4.621 and notify us about the results.

[AKRRKA]

Now I can reproduce memore leak with LinqConnect 4.4.621.
Here are links to video record the demonstration of the process.
Video_2014-11-16_154911.wmv - 73.9 MB
http://nashdisk.ru/e0c502

And profiling results from Red Gate ANTS Memory Profiler 8
ceContextStressTest-2014.11.16-15.43.amp8results
CRC32: FF06E084
MD5: C33B414C35CDBAF54A7CDE84AFD5A66E
SHA-1: A2BE2AC5367798394E9609B19F9AC1318B990E8F

ceContextStressTest-2014.11.16-15.43.Red Gate ANTS Memory Profiler 8.rar- 539.2 MB (WinRar 5 format!)
http://nashdisk.ru/eaa33b

The problem is reproduced on all the computers that I have tried with different configurations and operating systems. And this is a very serious problem.

If you can give me the opportunity to remotely connect to any of your computer through TeamViewer example, I could reproduce the problem on the first try.

Please contact me by email or skype to organize a remote demonstration.

Information about me and my contacts: http://habrahabr.ru/users/karen

[JBonsack]

Any news about this?

[AKRRKA]

No, no news. Nobody did not contact with me.

It is 100% reproducible problem. And a very bad problem as uncontrolled memory leak. For me, it is very critical.

I'm ready to show it on any computer. If have a computer on which the problem does not manifest it would be very good.

[MariiaI]

Sorry for the delay.
We have fixed the issue related to the memory leaks in LinqConnect. The fix will be included in the next public build of LinqConnect, which we plan to release in several weeks. We will inform you when it is available for download.

Also, we have prepared an intermediate build of LinqConnect with the fix for you and contacted you by e-mail regarding this.

[Zero-G.]

Hey

First of all, I am not a DevArt guy or something else!
Just want to give a thought on to your code snipset you provide.
First you call a Select for a complete set of data and then Loop through this data, look if some conditions are fulfilled and manipulate it.
So I would think that one of the Problems with this code could be, that for every entity a tracking object will be crated. This will blow up the complete Context.
2 soultions to this, just get the fulfilled data and manipulate it.
or create 2 datacontext. - One without TrackingEnabled=False and then manipulate it through "Attach" in the second DataContext.

Don't know, if it helps, but give it a Chance.

Have a nice day!

[JBonsack]

Hi,

could you please also send the intermediate of LinqConnect to me?
It is very urgent and critical to get a fix.


Best Regards,
Joerg

[MariiaI]

New build of LinqConnect 4.4.641 is available!
It can be downloaded from http://www.devart.com/linqconnect/download.html (trial version) or from Registered Users' Area (for users with active subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?f=31&t=30901.

[AKRRKA]

Fantastic! It looks like that is really a memory leak was fixed.

Screenshots:
Link to full image - 1


Link to full image - 2


Well, finally.
Thanks.