I've installed the SampleApps V207 and can start up the database and OID, but when trying to start WebLogic (via script 2-StartWLS.sh) it runs for a little while then pukes with an error that says it has run out of memory. I have 8GB RAM on my notebook and I've tried giving the VM 5GB of it but it still eats all the memory, pukes and dies. The deployment guide seems to indicate that 3.5 GB is the minimum (section 3.1). Has anyone had success with 4 or 5 GB?
Any troubleshooting suggestions would be appreciated.

right after starting the database.
It ran the same - consuming all memory until the Guru Meditation box popped up and let me kill the VM.
Is there a configuration in the WebLogic that I would need to tweek?

Jay;
Thanks for working with me.
This log file has several hundred lines. Is there something in particular I should look for?
Here are the entries just before it popped up the "Guru Meditation" box and died.

From the host system can you run msinfo32 to verify the min and max working process:

Click Start --> Run and type msinfo32

Expand Software Environment, and then click Running Tasks.
View the values in the Min Working Set and the Max Working Set columns for each process to determine the process that uses a lot of physical memory.

After the above steps are done launch the VM box and start the services. With this execise we will know if the issue is because of peaking out of memory or a different issue.

Lets say if the max working set is below 3 GB then try reducing the allocated memory of the VM box to 3 or 3.5 gb and try running the vm box.

I am at a loss as to what msinfo32 is supposed to reveal to me. I've tried running it and find that the process firesvc.exe (McAfee intrusion prevention) reports a min and max working set of 4194300 while virtualbox reports a minimum of 200 and maximum of 1380.
When I look in SysInternals Process Explorer, it reports that FireSrv has a working set of 23,000K, a peak working set of 60,000K and virtualbox (with just the database running) has a working set of 73,000K and peak working set of 86,000K. Inside the Vbox, I run top and with just the database running it reports 1,187,556K memory used.

When I run the WebLogic start up (2-StartWLS.sh) I can see the memory use in top slowly but surely climb until it consumes all available memory and then I get the guru box and VM crash that I mentioned in earlier posts. What is odd is that while the WebLoigc start script was running, I kept a window open in which I was running top with the processes sorted by VIRT. The database processes (command= oracle) where the ones that stayed at the top of the display with a consistent value of 1703 to 1730m.

I have been trying to figure out what tool to use to see what exactly is consuming the memory and I haven't been able to (yet). Any ongoing assistance you can provide would be much appreciated.

Jay;
I appreciate your assistance in helping to troubleshoot.
Are you still able to offer aid?
I've tried tweeking the VM memory size up and down - it makes no difference - Starting WebLogic causes the memory to be consumed and the Guru meditation box to pop telling me I've run out of memory.
Any insight you can offer to help me understand what is eating the memory would be appreciated.