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

Not enough storage is available to process this command

18 Answers 424 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Andy Taslim
Top achievements
Rank 1
Andy Taslim asked on 10 Aug 2010, 06:55 AM
Hi guys,

I always have compilation error about Telerik.Web.UI.dll, once in a day.
It is "Metadata file '....\Telerik.Web.UI.dll' could not be opened -- Not enough storage is available to process this command

Do you have any idea about it?

FYI: I am using trial version Q1 2010 Ajax

AGT

18 Answers, 1 is accepted

Sort by
0
Albert Shenker
Top achievements
Rank 1
Veteran
Iron
answered on 10 Aug 2010, 02:50 PM
I may be thinking of a different error, but I believe I have seen this before. In my case, it was probably caused by my computer being low on physical and/or virtual memory. In most cases, If I closed an app or two and then re-compiled, it worked fine. In extreme cases, I needed to reboot and then compile.
0
Andy Taslim
Top achievements
Rank 1
answered on 11 Aug 2010, 02:28 AM
But the question is, it always complaining about Telerik.Web.UI.dll... I never encountered error message with another .dll.
I am still thinking about the restriction of Telerik, since I am using trial version. Will it be possible?
0
Albert Shenker
Top achievements
Rank 1
Veteran
Iron
answered on 11 Aug 2010, 02:32 AM
you'll have to check with Telerik, then. In my case, it was the telerik.web.ui dll, since tha tis the only Telerik dll now.
0
Georgi Tunev
Telerik team
answered on 11 Aug 2010, 08:57 AM
Hi guys,

The cause of this error is discussed in this forum thread. It is a VS - related problem and unfortunately there is no elegant solution and you will need to restart the Visual Studio process in order to free the allocated memory or by increasing the memory size.



Best wishes,
Georgi Tunev
the Telerik team
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 Public Issue Tracking system and vote to affect the priority of the items
0
Rob
Top achievements
Rank 1
answered on 27 Feb 2012, 09:29 PM
That answer is unacceptable. This error is happening to me between 5 and 10 times a day. There has to be a better solution than restart Visual Studio.
0
Rumen
Telerik team
answered on 01 Mar 2012, 10:00 AM
Hello,

As noted earlier this is indeed a common Visual Studio problem that is not directly related to our controls. The problem comes from the fact that the Visual Studio executable is a 32-bit process and when the project that it tries to build is too large, it throws such error due to the lack of free memory. What I would suggest in addition to restart Visual Studio is to disable some addons like Reflector / Resharper / JustCode etc. that consume a lot of memory. If you are using a 64bit Windows there is a way to increase the memory allowance for the VS process, but the only way you can fix it on a 32bit system is to remove some projects from your solution or restart VS after the error occurs.

You can also try searching online for alternative solutions - google search.

Best regards,
Rumen
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.
0
Regeesh Joseph
Top achievements
Rank 1
answered on 26 Sep 2012, 10:50 AM
Hai,

I am not using any addons like Reflector / Resharper / JustCode etc. But I am getting this error even if no other applications  are opened. My system is equipped with 4GB of RAM. I am using a 32 bit system. 


0
Clinton Smyth
Top achievements
Rank 1
answered on 02 Oct 2012, 06:50 PM
The most plausible answer for this that I've found was posted by 'Anthony W Jones' on another forum:

"The error is misleading. It really should say "A large enough contiguous space in virtual memory could not be found to perform the operation". Over time allocations and deallocations of virtual memory space leads to it becoming fragmented. This can lead to situations where a large allocation cannot be filled despite there being a plenty total space available.

I think this what your "segmentation" is refering to. Without knowing all the details of everything else that needs to load and other activity which occupies the 2-3 hour period its difficult to say whether this really is the cause. However I would not put it into the category of unlikely, in fact it is the most likely cause."


.. either that or there's a memory leak in the Telerik code somewhere ;)


0
Regeesh Joseph
Top achievements
Rank 1
answered on 03 Oct 2012, 08:13 AM
All other high memory usage applications have no issues in over time allocations and deallocations of virtual memory space. Over time allocations and deallocations of virtual memory space leads to it becoming fragmented only when Telerik is used in the system !!!!!

0
ahmed
Top achievements
Rank 1
answered on 17 Oct 2012, 09:55 PM
As far as I have observed, this issue arise on 32bit windows when you are using telerik in embedded mode, since the dll size gets around 14.5 mb. This is extremely large size for a dll due to the resource (images, scripts etc) embedding.

This is the cost Telerik had to pay in order to provide ease of use. Either moving to 64 bit environment or using the resources out of the embedded mode solves the problem for me.

What surprises me is this issue comes on some PC while not on others without any apparent causes like free memory and disk space etc.
0
Regeesh Joseph
Top achievements
Rank 1
answered on 13 Dec 2012, 11:39 AM
Hai,

This issue comes frequently making it difficult to work. Recently, we upgraded to Q3 2012 version with the hope of eliminating this issue. We hope this issue will be solved in next version.

thanks & regards,
Regeesh
0
Chavdar Dimitrov
Telerik team
answered on 18 Dec 2012, 09:05 AM
Hi guys,

Thank you for sharing your experience regarding this.

I would suggest to disable the Telerik VSExtensions from the Extension Manager to see if this will affect the issue.

To to this open Visual Studio -> Tools -> Extension Manager and uninstall all Telerik extensions.

Let us know if this helps or the problem still occurs with the same frequency.

Kind regards,
Chavdar,
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.
0
Bruce
Top achievements
Rank 1
answered on 15 Mar 2016, 03:54 AM

Here we are in 2016 and still having the same problem (possible different reason)... but I cannot describe how upset i am with total loss of productivity.  When debugging, as soon as I change code (while stopped at a breakpoint) and then try to proceed (F10, F11, F5, etc.), I get the awful D:\Dev\TWO JINN\BMA 2.0\BMA2\lib\RCAJAX\2016.1.225.45.Trial\Telerik.Web.UI.dll cannot load.  out of memory  error.

 

I sent a separate post about this and attached a log file.

If i don't hear back soon, I will just remove Telerik so I can move forward.

0
Marin Bratanov
Telerik team
answered on 18 Mar 2016, 08:15 AM

Hello Bruce,

I am really sorry to hear that this issue is preventing you from working on your project.

The problem is that it stems from Visual Studio and not from our code, so we simply cannot fix it. The information collected in this thread is everything we have on the subject and I dare say that one of the best posts are from Clinton (on the exact nature of the issue) and Ahmed (on noting why the Telerik.Web.UI assembly has to be this large—at the time of writing we provide over 100 controls and 21 skins), in addition to the forum thread Georgi provided.

What I can suggest at this point is that you:

  • defragment your hard drive
  • increase the virtual memory
  • increase the physical memory allocated to VS

Regards,

Marin Bratanov
Telerik
Do you need help with upgrading your ASP.NET AJAX, WPF or WinForms projects? Check the Telerik API Analyzer and share your thoughts.
0
Bruce
Top achievements
Rank 1
answered on 18 Mar 2016, 04:10 PM

IContrary to what you say about it being a Telerik issue...

   I turned off JustCode and have not had the issue since.

Your suggestions are good generic suggestions.

I understand the first 2.

How do I increase physical memory allocated to VS?

0
Bruce
Top achievements
Rank 1
answered on 18 Mar 2016, 04:21 PM

Suggestion:

Create a smaller version of the assembly that is aprox half as large with only the most-frequently used controls & skins.

0
Marin Bratanov
Telerik team
answered on 21 Mar 2016, 05:04 AM

Hello Bruce,

Turning off VS extensions like JustCode is also discussed in this thread (see Rumen's post from the 1st of March 2012: http://www.telerik.com/forums/not-enough-storage-is-available-to-process-this-command#V33HssR5LUWT3LWApkQV8Q). Since you were still having this issue, I assumed you tried that or you did not use such plugins. The same post treats memory limitations (e.g., using 64bit OS and processes instead of 32 bit).

As for a smaller assembly—at the moment the Telerik.Web.UI is at its smallest possible size. It contains only the code for the controls (over 100, as I already mentioned) and a single skin (Default). This means the embedded resource count is at its absolute minimum so the controls can actually run and splitting the assembly would introduce a breaking change to absolutely all of our customers. The other problem this brings is that there is no universally acceptable logic we could use to split it (for example, should we leave data bound controls in one assembly, layout controls in another, input controls in a third one, and the common code shared across all controls in a fourth; or how do we determine the most used ones, apart from RadGrid).

I hope this clarifies the situation.

Regards,
Marin Bratanov,
Support Lead,
UI for ASP.NET AJAX

0
Bruce
Top achievements
Rank 1
answered on 21 Mar 2016, 04:34 PM

I am no longer experiencing the problem because (not sure which is more responsible)...

1) I increased the virtual memory block size from (aprox) 3485 to Window's "suggested" size 5440 (aprox).

2) I did figure out how to remove JustCode using VisualStudio settings.

Thx

 

Tags
General Discussions
Asked by
Andy Taslim
Top achievements
Rank 1
Answers by
Albert Shenker
Top achievements
Rank 1
Veteran
Iron
Andy Taslim
Top achievements
Rank 1
Georgi Tunev
Telerik team
Rob
Top achievements
Rank 1
Rumen
Telerik team
Regeesh Joseph
Top achievements
Rank 1
Clinton Smyth
Top achievements
Rank 1
ahmed
Top achievements
Rank 1
Chavdar Dimitrov
Telerik team
Bruce
Top achievements
Rank 1
Marin Bratanov
Telerik team
Share this question
or