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

Anyone else recieving OutOfMemoryExceptions with the new version

6 Answers 63 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
jdgoulden
Top achievements
Rank 1
jdgoulden asked on 11 Mar 2010, 01:09 AM
Been experiencing OutOfMemoryErrors on a project that was working fine with the Q3 release. Exception occurs when I compile the solution under VS2008 SP1. Anybody seeing anything similar? It gives me an error message referencing the command 

c:\program files\telerik\openaccess orm\sdk\VEnhance.exe -assembly:C:\Documents and Settings\cgouldj\Desktop\FPI.SetupUtility\SetupUtility\obj\Release\SetupUtility.exe -config:C:\Documents and Settings\cgouldj\Desktop\FPI.SetupUtility\SetupUtility\App.config -debug+ -verbose+ -reference:C:\Documents and Settings\cgouldj\Desktop\FPI.SetupUtility\DataAccessLayer\bin\Release\FPI.DataAccessLayer.dllC:\Documents and Settings\cgouldj\Desktop\FPI.SetupUtility\SetupControls\bin\Release\FPI.SetupControls.dll.

This will teach me to be on the bleeding edge

6 Answers, 1 is accepted

Sort by
0
jdgoulden
Top achievements
Rank 1
answered on 11 Mar 2010, 01:45 AM
Just a follow up for anyone else expereincing the same problem. I had uninstalled to Q3 ORM release and installed the new one. After updating the configurations and running the Check Settings utility I ws unable to build the same solution on either of 2 computers. After rebooting the PC, the build works correctly. Possibly something in the GAC.
0
Dimitar Kapitanov
Telerik team
answered on 11 Mar 2010, 03:27 PM
Hi jdgoulden,
We are happy you solved the problem, but we are really interested in having more information on the problem. Please if you have any insight in the situation or more information, do share it with us.

Regards,
Dimitar Kapitanov
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
jdgoulden
Top achievements
Rank 1
answered on 11 Mar 2010, 03:44 PM

Ths issue was occuring in a project where I had a class library with the Persistent objects and data access layer defined in it, and a second project that is using that library to access the database. The second project is a Winforms application where I am using RadControls for Winforms and it was the source of the issue. When I compiled the class library project there would be no problem, but during the compilation of the Winforms project referencing the class library, the I would receive an OutOfMemory exception and in several cases Visual Studio crashed. I actually have 2 computers that experienced the same thing, the problem stopped after I rebooted the affected PCs.

 

The actual problem appeard to be the VEnhance call, when the project enhancement is taking place, the crash occurs. I would strongly recommend rebooting the PC after an upgrade occurs.

0
Dimitar Kapitanov
Telerik team
answered on 11 Mar 2010, 03:56 PM
Hi jdgoulden,
Thanks for sharing that with us.

Greetings,
Dimitar Kapitanov
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
Jnchaves
Top achievements
Rank 1
answered on 01 May 2010, 10:21 PM
Hi,
  I am experiencing the same issue. I use the reverse mapping and start seeing memoy usage going higher and higher.
0
Ady
Telerik team
answered on 03 May 2010, 05:15 PM
Hi Amin Kanji,

 Do you get an OutOfMemoryException while building your Persistent classes project or while executing the Reversemapping wizard?

Can you attach a debugger (ClrDBG.exe) to the Visual Studio instance, enable 'Break when an Exception is thrown' and then execute the step that generates the error? You can send us the call stack if you get the error.
Here are the steps do attach the debugger
  1. Open the CLR debugger - dbgCLR.exe, and specify the existing Visual Studio process in 'Attach to Process' via the Tools menu
  2. Go to the 'Debug->Exceptions' menu item and check the 'CLR exceptions thrown' checkbox
  3. In the debugging options (available via Tools->Options->Debugging) uncheck the 'Enable Just My Code' option.
  4. You can now start debugging and execute the steps that reproduce the error and send us the call stack if you get an exception.

Do get back to us in case you need further assistance.

Greetings,
Ady
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.
Tags
General Discussions
Asked by
jdgoulden
Top achievements
Rank 1
Answers by
jdgoulden
Top achievements
Rank 1
Dimitar Kapitanov
Telerik team
Jnchaves
Top achievements
Rank 1
Ady
Telerik team
Share this question
or