This is a migrated thread and some comments may be shown as answers.

High Memory Usage

7 Answers 425 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Cezar
Top achievements
Rank 1
Cezar asked on 24 Feb 2016, 12:55 AM

Hi! I'm trying out Kendo UI cause the company where I work is intending to purchase it, but...

On my trial tests I can see Kendo UI has a big memory problem, and that will be decisive to buy it or not.

As you can see on the image attached, as soon as the web application starts Kendo UI is using 450MB+ of memory use!

I removed Kendo UI references and files from the test application and the memory problem vanished.

So, this confirms that the problem is occurring with Kendo UI.

If I have more than one web application (I tried with three test applications) each of them starts immediatly with 450MB+ of memory.

What should I do so Kendo UI uses less memory?

For me this is a HUGE problem.

What can you guys say about it?

You will find three images attached.

1) Showing the immediate memory usage on task manager;

2) The Kendo references on my project;

3) The Kendo files I'm using on my project bundles.

 

7 Answers, 1 is accepted

Sort by
0
Georgi Krustev
Telerik team
answered on 26 Feb 2016, 08:01 AM
Hello cpimentel,

In general, the w3wp process represents the IIS worker process that runs the Web application. I believe that the memory used in this case is mainly related to the ASP.NET MVC app you are running, because the UI for ASP.NET MVC library does not perform anything special in this case. 

The most consuming part of our library, in terms of memory, is the projection abstraction (ToDataSourceResult) built on top of the Linq expressions. But still the used memory is directly related to the amount of data you would like to project/manipulate. Again, we do not do any special here in order to accumulate additional memory.

Did you try to run the same app without using the UI for ASP.NET MVC? Could you send us a repro demo that we can run locally in order to observe the problematic behavior?

Regards,
Georgi Krustev
Telerik
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
0
Cezar
Top achievements
Rank 1
answered on 01 Mar 2016, 09:05 PM

Hello guys!

As asked, I've prepared a test solution to show the memory problem. Attached you will find the solution inside a rar file, and a new image of my task manager showing 500MB+ memory usage from the moment the web application is started.

You will also notice that the web application actually doesnt use anything from telerik. It only has a Home page and that's enough for the memory to increase dramatically.

If you remove Kendo UI references from the project, the memoey issue doesn't occurs anymore.

You will need Kendo UI DLLs to be referenced. I did not added those dlls to the rar files for obvious purposes.

These are the only two DLLs referenced:

Kendo.Mvc.dll

Kendo.Mvc.resources.dll

I'm looking forward to see your next reply.

Thanks in advance.

cpimentel

0
T. Tsonev
Telerik team
answered on 03 Mar 2016, 03:06 PM
Hi,

Thank you for sending the sample project. I think I see what's wrong.

The memory increase is due to the use of script bundling. This is known to cause memory usage spikes when bundling large, minified scripts such as kendo.all.min.js.

Removing the bundle will solve this problem. Another solution is to use plain bundles as suggested in the documentation.

Regards,
T. Tsonev
Telerik
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
0
Peggy
Top achievements
Rank 1
answered on 21 Sep 2016, 06:34 PM

Hi, we are having memory issues with many of our projects that use kendo.all.min.js. We had tried many of the suggestions in your documentation to no avail. Then we tried to make one of your demo's fail, and it fails exactly like our applications. We would appreciate your suggestions to fix this. I have attached a screen shots of the demo failing. http://demos.telerik.com/aspnet-mvc/grid/editing-custom 

Thanks!

0
Georgi Krustev
Telerik team
answered on 26 Sep 2016, 07:52 AM
Hello Peggy,

We tried to same demo using MS Edge and it seems to work as expected on our end. Probably we are missing something obvious. Could you send us a repro demo or if the live URL is enough, a repro steps that we can follow in order to replicate the issue? This information will help us to narrow the problem down and find the cause much faster.

Looking forward to hearing from you.

Regards,
Georgi Krustev
Telerik by Progress
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
0
John
Top achievements
Rank 1
answered on 27 Sep 2016, 08:13 PM

Hello Georgi,

I'm able to reproduce the issue with multiple demos, including this one - http://demos.telerik.com/aspnet-mvc/grid/index.  The fastest way I've found to create the issue is to keep clicking on the link for the basic usage grid (in the menu on the left) and IE memory usage climbs to around 1.6 GB before the page fails.  Alternately, I can repeatedly click refresh (F5) to keep loading the page to get the same result.  It takes me 3 - 5 minutes (around 30 page loads) to cause the error.  I'm using IE version 11.0.9600.18449 (update version 11.0.35) running on 64-bit Windows 7 Enterprise.  I can also reproduce the issues at home on a personal computer using a more recent version of IE 11.  Any suggestions or workarounds would be greatly appreciated.

Thank you for your help!

0
Georgi Krustev
Telerik team
answered on 30 Sep 2016, 07:34 AM
Hello John,

This is quite strange behavior. The "Basic demo" button is actually link (<a/>) that will perform full page reload. In this case we do not have any control over the memory usage. The described leak seems to be a browser problem, where it caches the page for some reason, which will cause the leak.

A quick research on the internet shows that the issue is hit by others too:

https://github.com/webcomponents/webcomponentsjs/issues/541#issuecomment-231826816

As it is stated in the message, it is an IE issue, which is reported. I hope that they will address this issue in future.

Regards,
Georgi Krustev
Telerik by Progress
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Tags
General Discussions
Asked by
Cezar
Top achievements
Rank 1
Answers by
Georgi Krustev
Telerik team
Cezar
Top achievements
Rank 1
T. Tsonev
Telerik team
Peggy
Top achievements
Rank 1
John
Top achievements
Rank 1
Share this question
or