out-of-memory

While running the VS 2012 application, getting an out of memory exception. This is occuring in debug and release mode and on initial load itself on my development machine. Even I'm getting the same error on a new asp.net (default) application I already looked at the solutions for similar issues on other threads and none of them worked in this scenario. Can some one help me on this? Exception of type 'System.OutOfMemoryException' was thrown. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the

In my Windows Phone 8 application I have a page with a LongListSelector which is bound to a list of 1000 objects having a property for base64string for image. Now to display the image, I wrote this converter to convert the bas64string into a stream . public object Convert(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture) { if (!value.ToString().Contains("http://")) { string str = value.ToString(); byte[] bytes = Converter.FromBase64String(str); using (MemoryStream stream = new MemoryStream(bytes)) { stream.Seek(0, SeekOrigin.Begin); BitmapImage image =

I know there is no simple answer to my question but I would appreciate ideas, guides or some sort of things-to-look-at list I have a net Windows service that is constantly throwing OutOfMemoryException. The service has two builds for x86 and x64 Windows. However on x64 it consumes a lot more memory. I have tried profiling it with various memory profilers. But I cannot get a clue what the problem is. The diagnosis - service consumes lot of VMSize and crashes app after 3 to 12 hours. The behaviuor is rather stochastic - there is no observable pattern for crash scenario. Also I tried to look at

I have a Java application that parses pdf files in a directory and its subdirectories and creates a database using the information found in the files. Everything was fine when I was using the program on around 900 files or so (which create a SQLite database with multiple tables, some of wihch contain 150k rows). Now I'm trying to run my program on a larger set of data (around 2000 files) and at some point I get "OutOfMemoryError: Java Heap space". I changed the following line in my jdev.conf file: AddVMOption -XX:MaxPermSize=256M to 512M and I got the same error (though later, I think). I'm

I have this java simulator that will need to handle a huge amount of data. It works fine, but one I get up to an array of int[100000][100][2] along with other big arrays. the program says that its out of memory. ( Java.lang.outOfMemoryError ) All fine and good, I just give it more memory, but It seems to always run out around ~300M even though I allow it 2GB. This is all from watching Task manager. Is there something wrong with my system, or is this just a java thing that I need to deal with? @DanielPryden OS: Win 7 32Bit 4GB of ram on board JVM Command: java -Xmx2048M -Xms2048M Simulator

This was working..and I moved the disposal code to the finally block, and now it fails every time. I have a test spreadsheet with 4 records, 6 columns long. Here is the code I'm using to bring it in. This is ASP .Net 3.5 on IIS 5 (my pc) and on IIS 6 (web server). It blows up on the line right before the catch: "values = (object[,])range.Value2;" with the following error: 11/2/2009 8:47:43 AM :: Not enough storage is available to complete this operation. (Exception from HRESULT: 0x8007000E (E_OUTOFMEMORY)) Any ideas? Suggestions? I got most of this code off codeproject, so I have no idea if

I am getting an OutOfMemoryError when I try to create a String larger than 4MB using StringBuilder.append() . As far as I know, StringBuilder doesn't have any limitations regarding size and so doesn't String . So I searched for "how to increase Android heap size" and as far as I could conclude from this answer and this answer , Gingerbread is the only version in which you have no way of dealing with the heap size, since for earlier versions you use the VMRuntime class and for newer versions android:largeHeap="true" on the Manifest. Is that assumption correct? What do you do when you're in

I test a mobile app and have been struggling with constant crashes of the app when I use an Android emulator. I have no problem on physical Android devices, but emulators crash several times per day. The app will crash quite consistently once I find a crash-prone part of the app's "workflow". But exactly where in the app will trigger a crash seems to vary from version to version. Here is the crash report : Android: 2.3.7 Model: Full Android on x86 Emulator java.lang.OutOfMemoryError: bitmap size exceeds VM budget at android.graphics.BitmapFactory.nativeDecodeStream(Native Method) at android