tags:

views:

56

answers:

2
+1  Q: 

f# interactive System.OutOfMemoryException

f# interactive throws System.OutOfMemoryException when loading large objects into memory.

Exception is thrown at approximately 1.3 gigs. Data set is 2.2 gigs, and loads fine in debugger mode.

Using VS2008 with April 2010 CTP

This is mostly a java library that is being used via ikvmc, but if that were an issue, it shouldn't be running in the debugger either.

+2  A: 

What is the question? What kind of data object are you loading (e.g. a large array of ints, or what)? Might be better to email fsbugs (at) microsoft (dot) com.

Brian  2010-06-09 20:12:36
It's a huge mix of all sorts of datatypes. I'll email them as you suggest
 2010-06-09 20:53:13
+1  A: 

The fsi.exe executable has a "32bit only" flag set. The flag can be removed to allow fsi.exe to run as a 64 bit process. http://cs.hubfs.net/forums/thread/6369.aspx

From James at Microsoft

 2010-06-11 17:36:25

related questions

CLR Profiler - Attaching to existing process
What's the maximum amount of RAM I can use in a Windows box?
.Net 2.0 - How efficient are Generic Lists?
Process Memory Size - Different Counters
C++ Memory management
Using MySQLi - which is better for closing queries
How Does A Stack Overflow Occur and How Do You Prevent It?
C Memory Management
How does .net managed memory handle value types inside objects?
FLVPlayback component memory issues
memset() causing data abort
Is Visual C++ memory managed by the Dot Net framework
Preventing Memory Leaks with Attached Behaviours
How to dispose a class in .net?
best way to persist data in .NET Web Service
Reading Other Process' Memory in Mac OS / BSD
Replicating load related crashes in non-production environments
Secure Memory Allocator in C++
Best way to wrap rsync progress in a gui?
Some kind of task manager for JavaScript in Firefox 3?
Of Memory Management, Heap Corruption, and C++
Understanding reference counting with Cocoa / Objective C
Setting Objects to Null/Nothing after use in .NET
Heap corruption under Win32; how to locate?
Anatomy of a "Memory Leak"